-
Notifications
You must be signed in to change notification settings - Fork 321
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 rules for this library #469
Comments
We are not using ProGuard, so we don't have recommended rules now. What I can say is when renaming packages, you will also need to rename package name strings here: msgpack-java/msgpack-core/src/main/java/org/msgpack/core/buffer/MessageBuffer.java Lines 62 to 64 in 1447f8f
Because msgpack-java uses reflection to load one of the MessageBuffer classes appropriate for each platform. |
Based on my knowledge ProGuard rules mentioned above should suffice. I will test these when next release rolls out in 3 weeks. |
An unexpected delay will need 2 weeks or so. |
No worries. Take your time. |
sad,it does not work。 -keep class org.msgpack.core.buffer.MessageBuffer {;} |
@keyguansz IIRC then the new rules are leaving the packages as they were. If I get time this weekend then maybe I will try to figure out more specific rules. |
In an Android app, we are fetching MsgPack from our API. What are the recommended ProGuard rules to use with this library?
The text was updated successfully, but these errors were encountered: