-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Android Crash with DexGuard enabled #7514
Comments
Hi @herisulistiyanto We provide our own Proguard configuration, which should be automatically applied, but in the past we have seen various issues between Proguard and Dexguard, so I suspect this is one of them. You can see ours here: https://github.com/realm/realm-java/blob/master/realm/realm-library/proguard-rules-consumer-common.pro I will need to investigate further to figure out exactly what could be wrong, but I suspect a temporary workaround would be to add
To your configuration |
Hi @cmelchior , thanks for the reply and suggestion. It seems in my case there are two classes need to be preserved with DexGuard 9.x enabled :
Because if i don't keep the
I've check both classes already annotated with |
Hmm, strange. Because our own configuration should account for that:
I wonder if our configuration is somehow not being applied? 🤔 |
Here's Realm DexGuard config i use :
the last two lines that solve the crash issue (other rules mostly the same rules from consumer-common.pro) For the stripped annotated class, it seem there is workaround with DexGuard configuration on post processing. It's already solved, thanks closing the issue |
SDK and version
SDK : Java
Version: 10.6.0
Observations
100% Crash at App Start (Fresh Install & Migration Scenario)
It happen in dev obfuscated with DexGuard 9.1.5
Yes, it is 100% reproduce-able
Build the App with DexGuard 9.1.5 enabled
Crash log / stacktrace
Steps & Code to Reproduce
Here's the DexGuard configuration :
AGP & Gradle Version :
Been tried to use another version of Realm-Java (6.1.0), facing the same crash issue.
Is there any clue about this issue?
Thanks
The text was updated successfully, but these errors were encountered: