-
Notifications
You must be signed in to change notification settings - Fork 47
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
permission problem.... #5
Comments
As message says, probably you have duplicated permission. Check permissions in the library Manifest here: https://github.com/iammert/FastGCM/blob/master/library/src/main/AndroidManifest.xml and compare it with your app permissions. If you notice duplicates, remove permissions in your app and let library set it. I'm not sure if it helps, but that's my guess. |
No way.... i get same error on two different apps that use fastgcm, any solutions? |
Did you guys tried @pwittchen 's solution. Library's Manifest.xml already has that permission. Did you try to remove this permission from your app module ? @sirvon @vicktor |
Yes.... but error remains.... |
@vicktor can you paste your manifest.xml here. |
I had the same problem!!!! |
@raulamoretti @vicktor @sirvon I just merged @raulamoretti 's commit. Can you guys try new version of library and ley me know if it is solved or not. |
@iammert It's still remain on version 1.1, any idea? |
Has this been fixed @iammert ? I have two apps using the library, and this issue will prevent the two app to coexist together. When I extract the compiled AndroidManifest.xml, both of them have
I'm expecting the package name in the permission to be changed to our own app package, but looks like this is there. |
Refers to the issue reported in http://stackoverflow.com/questions/27773143/can-i-remove-this-permission-it-cause-install-failed-duplicate-permission-in-a, this seems critical for the library. If for every App that uses FastGCM will end up having
Then this would be a problem in a long run, where user might not be able to install two apps that use this library. Perhaps the quick fix is to remove this permission from the library, and have user explicitly indicate on their own AnroidManifest file instead with it's unique package name? Thanks. |
Do you guys still get this error. You can use version 1.2. |
this error is popping up on all apps I have this lib in...
The text was updated successfully, but these errors were encountered: