-
Notifications
You must be signed in to change notification settings - Fork 108
No preview found in a minified and shrinked build (Proguard) #244
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
Comments
Resolved. Needed to use correct name of ShowkaseRootModule implementing class. Therefore:
Was not correct. Should have been.
|
@tomjegan Thank you for the tip 🥇 |
@tomjegan Is the single |
Just to summarize what's exactly needed for future reference - You essentially need to add a proguard keep rule to make it with in release/alternate builds. The exact keep rule depends on your setup. For example, if your
Then your proguard rule will need to be
We are essentially trying to retain the final Hope this makes sense! |
@tomjegan Thank you for your insights! Works great! 🚀 |
With direct reference to this issue we are also experience this problem with builds where we have pro guard enabled.
As per VincentJouanne's comments we also would like to enable showkase for our internal QA builds such that design/product can inspect the components in app.
We also want to shift the annotation processing away from our dev/debug build as the build times are too high for this tool to be valuable as is unfortunately (even with ksp enabled).
Is it possible to provide a set of rules which will stop all the functions required from from converted?
Have tried StylianosGakis's suggestion but does not appear to work for us. Have also tried:
But still seeing the error that there are no components.
Are we able to add in some default rules (or at least advise further in this instance) please?
The text was updated successfully, but these errors were encountered: