ANR from crashlytics related to Firebase #4345
Comments
|
I found a few problems with this issue:
|
|
Hi @graymind75, thanks for reporting. Are you using any code related to Crashlytics? Also were there any changes related to Firebase prior to this issue happening? |
|
No, It's just initializing with |
|
Thanks for the details, @graymind75. While we investigate this. Just to confirm, were you using a prior version of Crashlytics before experiencing this issue? If yes, could you share which version were you using? |
|
Hi, Sorry I forgot to put the versions and the devices ANR submitted from: |
|
Hi, we are facing the same ANR being reported twice with different logs: We use Crashlytics too and the versions are the ones that come with Firebase BOM They are our top ANRs, here are the stats of the last 30 days:
|
|
Same occurred to us as well with below logs: Firebase BOM Version - 31.0.2 |
Even after upgrading to BOM Version - 31.1.1 still the same. |
|
Is there any update on this issue, we are also facing a large volume of ANRs. |
|
We're seeing a similar issue with Firebase BOM |
|
We are aware of this issue. We have some work planned that will reduce the load on the main thread, which should resolve this issue as well. I will keep this thread updated. |
|
The issue started to surface roughly one year ago - surely you have the resources to do more than just "should resolve...". This is a product used by millions world wide and it really should get a higher priority. |
|
Hey @mrober, we appreciate the update. While we await a resolution, are you able to provide any workarounds to prevent this from occurring in the meantime? For example, temporarily disabling Firebase Analytics/Crashlytics? Any information would be useful, as we currently have an ANR rate that is 4X the PlayStore quality bar. |
is the problem with crashlytics or analytics? |
|
Same for me too. Stacktrace: |
|
@mrober please answer, In case a permanent solution will take some time, Do you have any temporary solution ? |
|
Hi @mrober, _JobScheduler reinforces callback and network behavior All ANR's which spiked in our app are on Android 14 , as mentioned in above chat threads, and mostly related JobScheduler. Strangely 75% of events are on OnePlus devices and rest 25% are on OPPO devices Here are the logs: art::ConditionVariable::WaitHoldingLocks main (native) This is becoming more critical now and shaken all our app's performance metrics in terms of ANR's Raised this to help you so that you can get more insights and request you to please provide us with the fix as soon as possible . |
Is this solved?, I'm also getting this ANR after android 14 migration |
|
Hi @mrober, Is there a release schedule? Our ANR rate is getting worse now. 😢 Thanks |
|
Seeing this on BOM |
|
Hi @mrober and @themiswang, It's been a few weeks, are there any new updates? |
|
Hey everyone, Sorry for the delay. We have been working on this, and have landed large changes to the SDK. Here is a beta version of Crashlytics SDK 19.2.0 which resolves several of the issues that have been causing ANRs. This version is different from 19.1.0 which will be released in the next day or so. 19.1.0 only includes some of these changes, but has gone through more validation. If you want to try the 19.2.0 beta, follow these steps: Download the artifact m2repository.zip and extract it to a local repo directory. Add something like the following to your app's gradle build files: // settings.gradle.kts
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
maven(uri("/path/to/local/repo/"))
google()
mavenCentral()
}
}// app/build.gradle.kts
dependencies {
implementation("com.google.firebase:firebase-crashlytics:19.2.0-beta01")
// ...
}The CHANGELOG is: * [feature] Added the `isCrashlyticsCollectionEnabled` API to check if Crashlytics collection is enabled.
* [fixed] Ensure that on-demand fatal events are never processed on the main thread.
* [fixed] Improved data consistency for rapid user actions.
* [changed] Internal changes to improve startup time.
* [changed] Internal changes to the way session IDs are generated.
* [changed] Internal changes to the way background tasks are scheduled.
* [changed] Migrated SDK to use standard Firebase executors.If you don't want to try the beta, you can wait for the stable 19.1.0 release in the next few days, which includes some of these changes. The full 19.2.0 release is undergoing further internal validation. |
|
When firebase-crashlytics:19.2.0 is going to be release?. we are hoping this will get release on BoM version |
|
When will 19.2.0 going to release? Since people are adopting to Android 14, seeing exponential increase in the counts. |
|
Any update ???? |
|
Is there an update about this? We rolled out and update with 19.1.0, but we're still seeing the same problems. |
|
Any update on the above getting multiple ANR due to this |
|
Morning everybody, Crashlytics 19.2.0 is scheduled to be released this week unless some delay happens. It will improve Crashlytics performance and mitigate the ANRs mentioned earlier in this issue. But it probably will not fix the Android 14 ANR because that is due to another Firebase dependency. That issue is also being worked on in #6147 and is a priority for them. If it can be completed and verified before the release it might be included. Otherwise, it will probably be an out of band release. I will update this issue after the release and let everybody know. |
|
@ChanakaWeerasinghe I cannot tell for sure due to the obfuscation, but I am pretty sure your issue was fixed in 19.1.0. Can you please check if you are on the latest version? |
|
Crashlytics 19.2.0 has finally been released. https://firebase.google.com/support/release-notes/android#latest_sdk_versions Crashlytics version 19.2.0:
|
|
@mrober So, 19.2.0 contains Android 14 ANR fix as well? |
@mrober Does 19.2.0 release include Android 14 ANR fix? Could you please confirm? |
|
Hey everybody, unfortunately 19.2.0 does not include a fix for the Android 14 issue. The Crashlytics ANRs have been addressed and I want to separate the two issues. So please check #6147 for the Android 14 issue, and I will close this issue for the Crashlytics ANRs. If you run into another another Crashlytics ANR, please submit a new issue. If you run into the Android 14 issue, please comment on #6147. |
Thanks for the update @mrober |
and others
[REQUIRED] Step 2: Describe your environment
Versions:
[REQUIRED] Step 3: Describe the problem
We facing this issue for almost 3 months now. But recently the ANR count is insanely high as you can see in the above
From crashlytics:
Relevant Code:
The text was updated successfully, but these errors were encountered: