-
Notifications
You must be signed in to change notification settings - Fork 606
FIAM: Fix FirebaseInAppMessagingDisplayErrorListener not being called #5719
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
📝 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 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
|
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
Please provide a description for the PR |
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.
Working to resolve issues
Cb developer
…#5719) Changed `GlideErrorListener` to a normal class and pass a new instance of the listener into each load image request instead of being injected as a defaultRequestListener. Refactored `InAppMessage` and `FirebaseInAppMessagingDisplayCallbacks` assignment code for clarity. Internal tracking: b/321732964 Issue: #5644
Changed
GlideErrorListener
to a normal class and pass a new instance of the listener into each load image request instead of being injected as a defaultRequestListener.Refactored
InAppMessage
andFirebaseInAppMessagingDisplayCallbacks
assignment code for clarity.Internal tracking: b/321732964
Issue: #5644