-
Notifications
You must be signed in to change notification settings - Fork 658
Merge master in to sessions-nine. #5440
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
Additionally, we are explicitly marking firebase-appcheck/test-app activity as exported, and removing direct dependencies it has with common and components.
…5408) * Added metadata to FirebaseInstanceIdReceiver to signal that it finishes background broadcasts after the message has been handled.
Co-authored-by: David Motsonashvili <[email protected]>
#5410) …mponent name. * Changed createMessagingPendingIntent() to create an Intent targeting the BroadcastReceiver via action and package instead of specifying the ComponentName directly. This will make it easier to change FirebaseInstanceIdReceiver's class name in the future.
Co-authored-by: Mark Duckworth <[email protected]> Co-authored-by: Ehsan Nasiri <[email protected]>
Changes: - Successful `GeneratePlayIntegrityChallenge` call should not reset `RetryManager` backoff - Cache in-flight App Check token fetching tasks - Update `403` errors to throttle with exponential backoff rather than a flat one-day period (to match [iOS](https://github.com/firebase/firebase-ios-sdk/blob/f3a14c249e001b3c894bb943ecc3973f50e60a49/FirebaseAppCheck/Sources/Core/Backoff/FIRAppCheckBackoffWrapper.m#L264-L268))
Fix Unity and Flutter on-demand user meta data behaviour. Cherry-picked from previous closed pr: #5275
Bump our Play Integrity API Library dependency version per the request of the Play Integrity team.
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Size Report 1Affected Products
Test Logs |
Coverage Report 1This report is too large (212,052 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
No description provided.