-
Notifications
You must be signed in to change notification settings - Fork 614
Add a CrashlyticsWorkers container to manage the workers #6178
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
Conversation
Release note changesNo release note changes were detected. If you made changes that should be |
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected Products
Test Logs |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Notes
Startup Times
|
firebase-crashlytics/src/main/java/com/google/firebase/crashlytics/internal/common/Utils.java
Show resolved
Hide resolved
...cs/src/main/java/com/google/firebase/crashlytics/internal/concurrency/CrashlyticsWorker.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woooh thank you for the refactoring!
…)" This reverts commit 9535f94.
Add a CrashlyticsWorkers container to manage the workers, and define what each one is for. Also added a
submitTaskOnSuccess
method for convenience. This will be useful for any of the user actions that get triggered by send unsent reports.Also found and fixed a bug in the worker queue. If a task gets cancelled and is followed by a runnable or callable already in the queue, it would have been skipped. Now it's not a problem, and a test case added.