-
Notifications
You must be signed in to change notification settings - Fork 625
Add Firebase Sessions Test App #4775
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
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.
LGTM
Size Report 1Affected Products
Test Logs |
Coverage Report 1This report is too large (200,795 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 |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Startup time comparison between the CI merge commit (df56408) and the base commit (1d6ab9d) are not available. No macrobenchmark data found for the base commit (1d6ab9d). Analysis for the CI merge commit (df56408) can be found at: |
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.
Thanks for the test app. This is a great way to validate our integrations.
Should we merge in the WebP files? Even if it is a boiler plate, can we skip them?
Curious question: I want to learn how the SDK behaves in a Jetpack Compose App. How can we achieve that? Should we need a separate app or just make a new app target which uses Jetpack compose?
Add Firebase Sessions Test App. This app will be used for local development, and eventually for CI automated tests.