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
Keep annotation does not keep class's constructor #1904
Comments
I tried |
However RealmException has all constructors. It's very comfusing
|
@skyisle It seems you have found a work-around. We'll examine and update the Proguard recommendations when we have a better solution. |
I think intended behavior of Keep annotation is keep everything include all method and constructors.
|
@skyisle Thanks for pointing us in the right direction. We'll update the documentation. |
@skyisle I confirmed your configuration keeps the constructors. I'll update out documentation. Thank you so much.
|
@skyisle It seems that What do you think? |
I update our documentation. If Thank you so much! |
@zaki50 You are right. I rechecked configuration with whyareyoukeeping proguard option.
It explains that constructor is included by
Thanks for quick response. |
Following crash reported for my app.
I used recommended proguard options on https://realm.io/docs/java/latest/#proguard
I think options should be changed to include constructors.
Decompiled RealmError does not contain constructor
The text was updated successfully, but these errors were encountered: