Skip to content
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

Sync-related classes are not excluded from Proguard correctly #643

Closed
edualonso opened this issue Jan 19, 2022 · 0 comments
Closed

Sync-related classes are not excluded from Proguard correctly #643

edualonso opened this issue Jan 19, 2022 · 0 comments

Comments

@edualonso
Copy link
Contributor

edualonso commented Jan 19, 2022

Having exceptions for sync-related classes in the library-sync Proguard consumer doesn't work. JavaClassGlobalDef has references to said classes when JNI is initialised, causing it to crash.

Said classes are all located under the cinterop module, which is shared across library-base and library-sync. Given that the JNI initialiser is only present for library-base, said exceptions must also be in the library-base Proguard consumer.

Additionally, RealmObjectCompanion had not been included from being stripped, resulting in crashes too as trying to retrieve companion objects from RealmObjects would cause crashes in release builds too.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant