-
Notifications
You must be signed in to change notification settings - Fork 623
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
ProGuard optimization causes "java.lang.VerifyError: Bad type on operand stack" #2719
Comments
We have exactly the same issue in our project. Any updates on this? |
Hi, we will try to investigate this problem soon |
@buehlerjochen, @wtlgo
|
Related issue in ProGuard Guardsquare/proguard#415 |
Disabled optimisation for descriptor field because in some versions of ProGuard, optimization generates incorrect bytecode that causes a verification error. Fixes #2719
@shanshin Sorry for the late response, Just tested you proposal and it seems to solve the issue. Thank you very much! |
Yeah, works for me too. Thank you! |
Describe the bug
If I try to optimize the application by disabling
I get the following error:
If I disable the optimization, though, everything works OK.
To Reproduce
Here's a project with reproduction: https://github.com/wtlgo/Kotlin-Serialization-Proguard
Expected behavior
It should work correctly either with or without optimization
Environment
com.guardsquare:proguard-gradle:7.5.0
The text was updated successfully, but these errors were encountered: