-
Notifications
You must be signed in to change notification settings - Fork 579
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
Make the session id not depend on fetching the fid #6152
Conversation
Release note changesThe following release notes were modified. Please ensure they look correct. Release Notesfirebase-crashlytics### {{crashlytics}} version 19.0.4 {: #crashlytics_v19-0-4}
* {{feature}} Added the `isCrashlyticsCollectionEnabled` API to check if Crashlytics collection is enabled.
([Github #5919](//github.com/firebase/firebase-android-sdk/issues/5919))
* {{fixed}} Ensure that on-demand fatal events are never processed on the main thread.
* {{changed}} Internal changes to the way session IDs are generated.
#### {{crashlytics}} Kotlin extensions version 19.0.4 {: #crashlytics-ktx_v19-0-4}
The Kotlin extensions library transitively includes the updated
`firebase-crashlytics` library. The Kotlin extensions library has no additional
updates. |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Coverage Report 1Affected ProductsTest 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
|
4880e1b
to
57aaf39
Compare
Make generating a session id not depend on fetching the fid. This is needed so we can allow the common worker to initialize, and start accepting use actions, before any data collection, settings, or fid validation happens.
The hash of the crashlytics installation id was used to pad the length and increase entropy. Instead of that, we use a random uuid now. Verified nothing depends on the source of that padding by manually setting it to all 0s and doing an end-to-end test.
The way the session id is built is a little bit weird, using bytes. In the future, we could rewrite this to use proper string formatting.