-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
2.8.6 breaks Android Proguard #1630
Comments
This reverts commit edbeb3e, as GSON 2.8.6 seems to have quite a bit of trouble: google/gson#1601 google/gson#1602 google/gson#1608 google/gson#1630 Let's wait for the dust to settle first. Change-Id: I7d0c7b671a31bf9bf3a1861cc56b009bd0f724b6 Signed-off-by: Robert Varga <[email protected]>
you need to change your module-info. |
Can you please check if this issue still occurs with the latest Gson version? The way the |
I am going to close this because no answer has been provided. If you still experience this with the latest Gson version, feel free to comment here again with more details. |
In my app, proguarding fails when I use gson 2.8.6, some NullPointerException, without any info, it does not even say it is from gson, but when I downgrade to 2.8.5, it is fine as it has been.
One visible warning is that "module-info.class" appears more than once. I see in some commits that you have added the module-info file in this release.
I found no workaround for proguard.
This is the proguard that is bundled with Android Studio / Android SDK, I don't know which version it is. It is possibly a bug in proguard but despite loading quite a few other libraries, it fails only with gson (I do not know if the other libraries have a module-info file in there).
The text was updated successfully, but these errors were encountered: