Is anyone who is using Raygun in their Android apps seeing this error exception:
java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/conn/util/InetAddressUtils;
at main.java.com.mindscapehq.android.raygun4android.messages.NetworkInfo.readIPAddress(SourceFile:117)
at main.java.com.mindscapehq.android.raygun4android.messages.NetworkInfo.<init>(SourceFile:20)
at main.java.com.mindscapehq.android.raygun4android.messages.RaygunMessageDetails.setNetworkInfo(SourceFile:61)
at main.java.com.mindscapehq.android.raygun4android.RaygunMessageBuilder.setNetworkInfo(SourceFile:81)
at main.java.com.mindscapehq.android.raygun4android.RaygunClient.buildMessage(SourceFile:508)
at main.java.com.mindscapehq.android.raygun4android.RaygunClient.send(SourceFile:221)
This exception is very intermittent, but when it does happen, it always occurs when the app calls RaygunClient.send(...). I'm using Raygun in my app to report error conditions such as a failed webservice call, however, when I report this to Raygun it crashes my app!
The release of v3.0.6 includes fixes that address the problems seen with InetAddressUtils NoClassDefFoundError exceptions. Please update to release v3.0.6 and let us know if the problems persist.
Please see our documentation on how to update. https://raygun.com/documentation/language-guides/android/crash-reporting/installation/
Regards,
Mitchell.
Related
So I'm trying out xamarin in VS2017, but found this undhandled error:
Unhandled Exception:
Java.Lang.SecurityException: <Timeout exceeded getting exception details>
This is very clueless. How can I get the full information of the runtime error like in Android Studio?
I had the same problem while calling some native API,
solved it by
Put a try catch around the block of got which is throwing the error.
Put a breakpoint in the catch block, you can get actual details of the exception.
After getting assistance from Microsoft, I finally found the solution.
TL;DR
Use VS Android device log and filter with "mono-rt" or "Error"
Complete Answer:
There are 2 solution:
1. Using Android Studio logcat:
Open the Android Studio logcat (View > Tool Windows > Logcat). From the logcat window, choose the device, choose the Xamarin.Android deployed application, and choose logcat for Error
Android logcat will display the runtime error:
2. Using Visual Studio Android Device Log:
Open the Visual Studio Android Device Log(Tools > Android > Device Log).
Here is the tricky bit: Unlike Android Studio, VS list all of the device log, not limited to the Xamarin.Android app deployed. So somehow we have to use the filter to get the relevant information. The problem is, what filter should we use? I used my application name and the error didn't show up. It turns out that when the error happen, the log doesn't contain any of the application name. Instead it has "mono-rt" tag with "Error" type.
So there you have it. Filter it with "mono-rt" tag or "Error" type and you will find the error information
Crashlytics compile('com.crashlytics.sdk.android:crashlytics:2.4.0#aar') is integrated with the app and is being tested on nexus 7 4.4.4,
The crash is seen from application onCreate method and following stacktrace is obtained. No other similar error/explaination could be found on stackoverflow.
Any suggestions are welcome.
Caused by: java.lang.TypeNotPresentException: Type com/crashlytics/android/core/internal/CrashEventDataProvider not present
at java.lang.Class.getDeclaredAnnotation(Native Method)
at java.lang.Class.getAnnotation(Class.java:290)
at io.fabric.sdk.android.Kit.containsAnnotatedDependency(Kit.java:158)
at io.fabric.sdk.android.Kit.compareTo(Kit.java:140)
at io.fabric.sdk.android.Kit.compareTo(Kit.java:33)
at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:291)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:153)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:142)
at java.util.Arrays.sort(Arrays.java:1970)
at java.util.Collections.sort(Collections.java:1864)
at io.fabric.sdk.android.Fabric.initializeKits(Fabric.java:401)
at io.fabric.sdk.android.Fabric.init(Fabric.java:375)
at io.fabric.sdk.android.Fabric.setFabric(Fabric.java:332)
at io.fabric.sdk.android.Fabric.with(Fabric.java:303)
at com.xxxx.MainApplication.onCreate(MainApplication.java:19)
Apparently android limiatation of 65K methods is the problem on pre-lollipop devices, the problem is not due to crashalytics library per-se but in general one might run into this problem due to limitation of 65K methods at dalvik level.
Thanks to http://frogermcs.github.io/MultiDex-solution-for-64k-limit-in-Dalvik/ I was able to get the no. of methods in my .apk file.
When in a call using the Sinch SDK on Android, the following error is thrown:
09-14 17:06:38.223 28454-28484/com.callcasual.callcasual E/sinch-android-rtc﹕ ERROR ; (17: 6:38:237 | 1) 28493; (voe_audio_processing_impl.cc:857): GetEcMetricsStatus: not supported
When searching for that error it appears to be an issue with WebRTC, however I cannot find a way to solve the issue.
This is only indicating that echo metrics are not available, the voice will go through fine during the call anyway. Why WebRTC logs this as an error I'm not sure but we are looking at disabling this in a future release of the Sinch SDK.
I'm not using any provider in my application, however i'm getting the error:
05-20 13:48:08.695 5003-5136/com.example.myapp E/ActivityThread﹕ Failed to find provider info for com.example.myapp
This error doesn't break the app but its strange because it show only my application package without a class, and the problem occurs only in samsung galaxy y duos...
Could it be any other app? A library in project?
This is bothering me
Found the problem, was the MobileAppTracking API in the method trackAction. At least this doesn't break the app, but is a weird message in the log...
I was able to use the native debug functionality until recently. I've been coding in java and went back to the native code but now I can't native debug. It will run and with the previously working debug config but I get a Null Pointer error on launch right when it would be attaching:
'Launching [debug config]' has encountered a problem.
An internal error occurred during 'Launching [debug config]'.
java.lang.NullPointerException
The app will run on the device, but won't hit breakpoints. Anyone seen this, it's driving me nuts?
Turns out this was due to the manifest "debuggable" being set to false. When you don't run native it tells you exactly that. With native, you get the absolutely useless error. I'll put in an enhancement request.