-
Notifications
You must be signed in to change notification settings - Fork 64
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
Running monkey on release variant to detect any Proguard misconfiguration #644
Conversation
…library-base proguard consumer file as they are needed when instantiating JNI's JavaClassGlobalDef. Additionally added a step to CI where the monkey runner is executed on the release sample app instead of the debug one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch 👏, I think you forgot to either rebase on top of my branch or add the commit that modifies the Jenkins file to run monkey against the release variant
kotlinx.serialization.KSerializer serializer(...); | ||
} | ||
|
||
# Change here com.yourcompany.yourpackage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rules below were accidentally copied from the Bookshelf app
🤦 that's right. I've already changed it. It will hopefully be fine on CI, since I ran it like 10 times on my machine yesterday. |
Fixes #643
Moved Proguard sync-related exceptions located under
cinterop
to thelibrary-base
Proguard consumer file as they are needed when instantiating JVM'sJavaClassGlobalDef
.Added missing exceptions for
RealmObjectCompanion
andJVMScheduler
as well since it was also causing similar crashes.Added a step to CI where the monkey runner is executed on the release sample app instead of the debug one to catch these types of Proguard issues.