-
Notifications
You must be signed in to change notification settings - Fork 90
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 problems #39
Comments
Strange. Are you building from source or using the aar from Maven central? |
It seems like my changes of directory names to lowercase was not commited to the repo. |
I am using Eclipse, so I've not bothered setting up the projects but simply extracted the jar files from the aar's from the Maven web page. I also just tried with the jars from 0.15 and they worked. Both failed classes (BuildConfig and R) are generated by the android tools and I see that in AndroidManifest.xml, you have the code below. If you fix the casing there, it'll probably work.
|
I don't get the same errors as you do, but I'm using Android Studio. |
I don't know if those classes are required. What are they used for? SignalA don't use any resources so I guess that the R class is not used at all. |
R is, as you say, resources. BuildConfig contains (from what I've found on the web) a flag to tell the code if it is in debug mode or not. I guess neither of them is needed if you don't use the debug flag or resources. |
fixed in version 0.20 |
Please, start a new issue. This does not seem to be a ProGuard problem. |
How can I do with the Message loss ,The.Net server receives can not receive, the Android client can not receive |
I get the following errors when using ProGuard on a project using SignalA 0.16. I haven't tried it with earlier versions of SignalA but from the output I can guess it is because of the "Changed package names to lowercase" change.
The text was updated successfully, but these errors were encountered: