Getting this issue in firebase crashalytics only for android 12,
jdk.internal.misc.Unsafe.park
This is logs :
main (timed waiting):tid=1 systid=17547
at jdk.internal.misc.Unsafe.park(Native method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1079)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1369)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:278)
at com.google.firebase.crashlytics.internal.common.Utils.awaitEvenIfOnMainThread(Utils.java:126)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController.handleUncaughtException(CrashlyticsController.java:232)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController$1.onUncaughtException(CrashlyticsController.java:154)
at com.google.firebase.crashlytics.internal.common.CrashlyticsUncaughtExceptionHandler.uncaughtException(CrashlyticsUncaughtExceptionHandler.java:55)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1073)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
at java.lang.Thread.dispatchUncaughtException(Thread.java:2306)
I m using crashalytics and getting this at crashalytics and i expect no crashes like this or ANR.
which version you are using for firebase crashalytics?
Related
I faced DeadSystemException in app on Huawei devices when HMSPackageManager tries to get info about services from Android PackageManager.
Stacktrace:
Fatal Exception: java.lang.RuntimeException: android.os.DeadSystemException
at android.app.ApplicationPackageManager.queryIntentServicesAsUser(ApplicationPackageManager.java:1192)
at android.app.ApplicationPackageManager.queryIntentServices(ApplicationPackageManager.java:1198)
at com.huawei.hms.utils.HMSPackageManager.f(HMSPackageManager.java:27)
at com.huawei.hms.utils.HMSPackageManager.i(HMSPackageManager.java:4)
at com.huawei.hms.utils.HMSPackageManager.refresh(HMSPackageManager.java:16)
at com.huawei.hms.utils.HMSPackageManager.getHMSPackageName(HMSPackageManager.java:8)
at com.huawei.hms.utils.HMSPackageManager.getHmsVersionCode(HMSPackageManager.java:1)
at com.huawei.hms.utils.HMSPackageManager.isApkUpdateNecessary(HMSPackageManager.java)
at com.huawei.hms.adapter.AvailableAdapter.isHuaweiMobileServicesAvailable(AvailableAdapter.java:77)
at com.huawei.hms.common.internal.BaseHmsClient.checkAvailabilityAndConnect(BaseHmsClient.java:134)
at com.huawei.hms.common.internal.BaseHmsClient.connect(BaseHmsClient.java:1)
at com.huawei.hms.common.internal.HuaweiApiManager$ConnectionManager.connect(HuaweiApiManager.java:97)
at com.huawei.hms.common.internal.HuaweiApiManager$ConnectionManager.sendRequest(HuaweiApiManager.java:96)
at com.huawei.hms.common.internal.HuaweiApiManager.connectAndSendRequest(HuaweiApiManager.java:37)
at com.huawei.hms.common.internal.HuaweiApiManager.handleMessage(HuaweiApiManager.java:35)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:213)
at android.os.HandlerThread.run(HandlerThread.java:67)
Crash occurs on Android 8/9/10/11, so likely it's not android problem. Crash happens only on Huawei devices. Our app not call HMSPackageManager from any place, so I think it happens in time of HMS Core initialization.
Is anyone has same problem?
Huawei support said that problem in Android OS, but they try to fix error in next HMS SDK update in mid of september.
I updated to the latest Crashlytics libs and it seems the crashes are not reported on the website.
Bellow is my logcat when starting the app, I cause a native crash then restart the application. Log shows like the report was uploaded but I can't see it anywhere.
libcrashlytics: Initializing libcrashlytics version 2.0.0
libcrashlytics: Initializing native crash handling successful.
CrashlyticsCore: Initializing Crashlytics 2.5.0.20
CrashlyticsCore: No minidump data found in directory /data/user/0/.../files/.Fabric/com.crashlytics.sdk.android.crashlytics-ndk/native/1515762319997
-----> I cause native crash here
libcrashlytics: Initializing libcrashlytics version 2.0.0
libcrashlytics: Initializing native crash handling successful.
CrashlyticsCore: Initializing Crashlytics 2.5.0.20
cr_CrashFileManager: /data/user/0/.../cache/WebView/Crash Reports does not exist or is not a directory
CrashlyticsCore: Crashlytics report upload complete: 5A58B63A034F-0001-0EA0-1EF6E7C2180A
Initially I tried a older version and had some success with it but after upgrading to the latest then going back to the older version that stopped working too. The old version no longer shows a "upload complete" message.
Can you please help, I trying to get this working for 2 days...
Thank you for any help.
I had the same problem, and after searching for a few hours, I solved it by updating my "google-services.json" file that was not the latest version
I am using FCM and while run the app it crashes at FirebaseInstanceId.getInstance().getToken() line and gives below error :
E/AndroidRuntime: FATAL EXCEPTION: main
java.lang.NoClassDefFoundError: com.google.firebase.FirebaseApp
at com.google.firebase.iid.FirebaseInstanceId.getInstance(Unknown Source)
Can anyone help me for solve this issue?
You have to enable the API in Google project console ,and also create the keys which required for FCM from your project console.
Also try to Uninstall your app once and check,because onTokenRefresh() will call once,
Please follow the below link for more information.
https://developers.google.com/cloud-messaging/android/android-migrate-fcm
Please check below once --
Use Google Play services 9.0.0
Android Studio 1.5 or higher
An Android Studio project and its package name.
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.
I have started getting the following exception on some devices:
java.lang.NullPointerException
at com.mycompany.iab.IabHelper.queryPurchases(Unknown Source)
at com.mycompany.iab.IabHelper.queryInventory(Unknown Source)
at com.mycompany.iab.IabHelper.queryInventory(Unknown Source)
at com.mycompany.iab.IabHelper$2.run(Unknown Source)
at java.lang.Thread.run(Thread.java:856)
And I'm wondering if maybe I using the wrong version of the IABHelper as all the posts I find about that same exception are pretty old.
Thanks.
It looks like you probably are using the latest version. Though check the version number in the SDK manager is version 5, then perform a diff on the util folder you have in your app. I am getting these errors too - I assume that it is user error (not calling the sample APIs correctly in some way or other). I got 2 reports today, and 1 at the end of October (2014) - not many so far...