Fix for java.lang.IllegalAccessError: Interface androidx.lifecycle.c #547
Merged
Conversation
Contributor
|
Hmm R8/Proguard shouldn't remove a class when it's being used, but it should obfuscate it. Honestly I'm not sure why obfuscating it would cause this error... But the link you posted about the issue in the flutter plugins repo seems to be the same and that seems to have fixed it, so maybe it's an issue in R8 as they posted... Anyway, I think this is ok 👍 |
Jethro87
pushed a commit
to Jethro87/purchases-flutter
that referenced
this pull request
Jan 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes sure
androidx.lifecycle.DefaultLifecycleObserverdoesn't get stripped out by R8.We got reports of this in https://play.google.com/sdk-console/u/1/accounts/3894912036640479868/sdks/8672516042485634097/crashes/347b470a/details?timeRange=LAST_28_DAYS&installSources=PLAY_STORE&crashStatus=SDK_CRASH_STATUS_UNSPECIFIED and also via support. The stacktrace looks like:
I found reports of this in:
I will port this change all the way down to purchases-android, but I would like to ship it first for Flutter since I think most affected apps will be Flutter.
I built a Flutter app on release mode and it looks like the class is there after this change:
I can't see the class when analyzing the apk before this change, but I am not sure if it's due to it being renamed or something.
I wasn't able to reproduce the stacktrace, but I am pretty optimistic this will fix it.