Skip to content
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

Fix crash when receiving IAM on android #1264

Merged
merged 1 commit into from
Feb 12, 2021

Conversation

gonzalonarbaiz
Copy link
Contributor

@gonzalonarbaiz gonzalonarbaiz commented Jan 26, 2021

The range that we were using was causing that gradle build to use version 20.2.2 of the firebase messaging library, which was making the app crash.
That error is fixed on later versions of the library.
This error is reported in https://firebase.google.com/support/release-notes/android#messaging_v20-2-2

This change is Reviewable

…cking 20.2.2 that was causing the app to crash.
@@ -5,7 +5,7 @@ ext {

androidXVersion = '[1.0.0, 1.99.99]'
androidWorkVersion = '[2.0.0, 2.99.99]'
firebaseMessagingVersion = '[19.0.0, 20.99.99]'
firebaseMessagingVersion = '[19.0.0, 21.99.99]'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you put more information about the error and what specific under this version solve the problem?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there is a known issue https://firebase.google.com/support/release-notes/android#messaging_v20-2-2 and we are asked not to use this version. For some reason I couldn't find when the version range is set to [19.0.0, 20.99.99] on my builds didn't go for 20.3.0 which already has a fix for that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkasten2 FYI

@Jeasmine
Copy link
Contributor

Jeasmine commented Feb 9, 2021

It seems like users are facing this issue check #1267 this should be merge and ready for the next release

@gonzalonarbaiz gonzalonarbaiz merged commit 2ea9ea2 into master Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants