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

proguard configuration #593

Closed
craig-at-rsg opened this issue Aug 21, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@craig-at-rsg
Copy link

commented Aug 21, 2015

Can someone share a proguard configuration that works for this project? My maps work fine until I try them in a release build, and from error messages it looks like obfuscation is the problem.

@craig-at-rsg

This comment has been minimized.

Copy link
Author

commented Aug 21, 2015

Adding this seemed to do the trick for me (I also needed to handle the fact that the API keys are based on which keystore you use, and I had debug and release keystores):

-keep public class * extends plugin.google.maps.MyPlugin
-keepclassmembers public class plugin.google.maps.GoogleMaps {
*;
}
-keepclassmembers public class * extends plugin.google.maps.MyPlugin {
*;
}

@Alex-Sessler

This comment has been minimized.

Copy link
Contributor

commented Mar 9, 2016

you are awesome! thanks for sharing!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.