No preview found in a minified and shrinked build (Proguard)
See original GitHub issue👋 Thanks guys for the amazing work on Showkase, we have implemented it in our apps: we use it to quickly see if we missed the implementation of our components.
Problem
When we launch the showkase activity, it does not find any preview.

Expected behavior
When we launch the showkase activity, it finds all composables annotated with @Preview
.
Hypothesis
It is ok in debug but ko in release. Do you think we should specify something in proguard settings ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9
Top Results From Across the Web
Shrink, obfuscate, and optimize your app - Android Developers
Learn how to shrink code in your release build to remove unused code and resources.
Read more >What does 'minifyEnabled=true' do when all configuration ...
Everything is working fine except if I enable minification in my app/build.gradle via minifyEnabled true the app instantly crashes on startup ...
Read more >Android MinifyEnabled, Obfuscation and Shrink | by Burak iren
Specifies not to shrink the input. By default, ProGuard shrinks the code: it removes all unused classes and class members. It only keeps...
Read more >Configuring ProGuard | CodePath Android Cliffnotes
ProGuard is a tool to help minify, obfuscate, and optimize your code. It is not only especially useful for reducing the overall size...
Read more >Debugging Proguard configuration issues
First of all, we need to be sure that the issue we have is because of some misconfiguration of the release build. To...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sounds reasonable! I’ll take a look at share the keep rules you might need!
Hey! I had played around with the proguard configuration a bit and went down a rabbit hole for minimizing the footprint of this library. I was also experimenting with using
debugImplementation
and updating some of the documentation to reflect with some new guidance for use cases where Showkase is only used in debug mode. As far as release builds go, I haven’t profiled release build yet and suspect that it’s probably going to be the rule that you have in your previous comment itself. Once more people can confirm it and I also spend some time experimenting with it, I can potentially ship this library with some release proguard rules.