Bug P3
Status Update
Comments
da...@google.com <da...@google.com> #2
I'm not sure how to edit the description. But forgot to add that this will work when the app is in the foreground. It just doesn't work when you lock your device. I test this by moving the app to the background and then locking my device and checking the logs in Android Studio.
va...@grabtaxi.com <va...@grabtaxi.com> #3
We’re encountering a similar issue with our FileUploadWorker, which is constrained to run only when the network is available. After this version bump, we’ve noticed that our file uploads are failing due to DNS network errors, which have increased by 5x. This could be a result of the UploadWorker starting and resuming even when there’s no network connection. Looks like this recent commit may be related to the issue : https://android.googlesource.com/platform/frameworks/support/+/8aa67b30ea5e50b3c0e89909990b5f53d159465d
It would be great if you could prioritize a fix for this issue. Additionally, if there are any alternative ways we can address this from our side, please let us know. Thank you!
It would be great if you could prioritize a fix for this issue. Additionally, if there are any alternative ways we can address this from our side, please let us know. Thank you!
Description
Auto-Restart Crash Loop
Issue Summary
We identified a critical crash pattern in Firebase Crashlytics where a small subset of users experienced an unusually high number of repeated crashes. While the issue affected relatively few users, each affected user generated thousands of crash reports, all occurring during application launch.
Investigation
Initial Observations
Reproduction Steps
To investigate the issue, we:
Root Cause
The investigation revealed that:
Component used:
Version used: 2.8.0
Devices/Android versions reproduced on (check emulator_spec.txt)
Those crashes could not be fixed because they were device-specific issues. However, we hope to prevent repeated crashes. Please provide any advice to fix or workaround.