-
Notifications
You must be signed in to change notification settings - Fork 4k
fix(messaging): revert change to getParcelableExtra()
that may result in crash
#11163
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
@@ -5,7 +5,7 @@ buildscript { | |||
} | |||
|
|||
dependencies { | |||
classpath 'com.android.tools.build:gradle:8.0.1' | |||
classpath 'com.android.tools.build:gradle:7.4.1' |
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.
I think we can keep gradle 8.0.1, it shouldn't cause issues
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.
I'm afraid it does cause issues, it requires Java 17
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.
But this is the gradle file of the example app, should not impact the release
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.
True, it won't impact the release, but anyone trying to build the example app won't be able to without java 17. It's an easy win.
getParcelableExtra()
that may result in crashgetParcelableExtra()
that may result in crash
I get this error using firebase_messaging: ^14.6.2, on every second notification received. |
Description
Very hard to debug why the crash occurs, but it happens from time to time so reverting back to previous implementation for now to resolve the issue.
Related Issues
fix: #11142
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?