-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FirebaseCrashlytics] ANR in FirebaseSessionsRegistrar #6523
Comments
Hi @pritesh-swiggy, thanks you for reaching out. I tried reproducing the issue, however, I did not encounter any ANR issue. By any chance, are manually initializing the Firebase SDK? Can you share an MCVE? That'll help us to investigate the issue. Aside from that, are you constantly experiencing this error? Does the issue occur on certain devices and/or android versions? Thanks! |
Hi @lehcar09, We're not initialising SDK manually, we're using This issue is happening for 100% Android 14 users in 100% background state. Also we have started seeing this issue after the recent bump of crashlytics SDK from Our targetSDK is also 34 (Android 14). We're also seeing some other ANRs along with this SDK bump ANR 1. com.google.firebase.tracing.ComponentMonitor.lambda$processRegistrar$0Happening for Android 10, 11, 12 users in 100% background state
ANR 2. com.google.android.datatransport.runtime.DaggerTransportRuntimeComponent$TransportRuntimeComponentImpl.initializeHappening for Android 11, 12, 13 users in 100% background state
Do let me know if more info required |
Thank you for additional details @pritesh-swiggy. Looking into the other ANR you’re encountering, It looks to me that this is related to the ANR issue that we investigated. According to our engineers (#6147#issuecomment-2417385067),
As for the ANR issue from FirebaseSessionRegistrar, were you able to reproduce the issue? Is there any chance you can share an MCVE? |
Hi @lehcar09, We're not able to reproduce the same issue. We're receiving the ANR stack traces from the Firebase and Play Console. Are we tracking this issue internally somewhere? probably happening to other clients also. |
Thank you for your clarification. I've checked our records and haven't found any similar reports of ANR issues related to FirebaseSessionsRegistrar. To help our engineers investigate further, could you please confirm the version of FirebaseSession you're currently using? I've notified our engineering team about this issue and will keep you updated. |
Hi @lehcar09, Thanks for an update, Firebase Crashlytics version 19.2.0 uses firebase-sessions version |
Hi @lehcar09, did you get a chance to check this? can you share an update? |
Hi @lehcar09, can you help with an update on this issue? |
Hi @pritesh-swiggy, I have raised this issue to our engineers and we're already looking into it. I'll get back to you as soon as we have updates. |
We face the same issue with a more apparent stack trace. I hope this helps solve the problem.
|
Hi, @lehcar09, can you share an latest update on this issue? |
Step 2: Describe your environment
Step 3: Describe the problem
Steps to reproduce:
Relevant Code:
The text was updated successfully, but these errors were encountered: