INSTALL FAILED DUPLICATE PERMISSION C2D MESSAGE

Question

I am using Google notifications in my app  and until now I have done below in the manifest    lt  -- GCM -- gt   lt uses-permission android name  android permission GET ACCOUNTS    gt   lt  -- GCM requires a Google account  -- gt   lt uses-permission android name  android permission WAKE LOCK    gt   lt  -- Keeps the processor from sleeping when a message is received  -- gt    lt uses-permission android name  com google android c2dm permission RECEIVE    gt   lt  -- This app has permission to register and receive data message  -- gt     lt  -- Creates a custom permission so only this app can receive its messages  NOTE  APP PACKAGE permission C2D MESSAGE -- gt      lt permission android name  com myapp permission C2D MESSAGE  android protectionLevel  signature    gt   lt uses-permission android name  com myapp permission C2D MESSAGE    gt       lt  -- END GCM -- gt    It worked perfectly until I updated my Nexus 7 to Android 5 0  Now when I try to install the app in this device with Eclipse  I get this error      INSTALL FAILED DUPLICATE PERMISSION perm com myapp permission C2D MESSAGE pkg com myapp   I don t understand what is wrong  It was working perfectly until Android 5 0  I know that I am using C2D MESSAGE in two lines  permission and uses-permission but I have copied that code from the original Google GCM guide  so it must be fine

User · Answer

I ve solved this without having to resort to uninstalling the alternate apk first  what a pain  right    To successfully install both a debug and release version of an apk  simply use gradle s built-in   applicationId  placeholder within the AndroidManifest xml to modify the permissions  android name values at compile time   The build gradle file snippet   buildTypes       debug           applicationIdSuffix   debug                        The AndroidStudio xml file snippet    lt uses-permission android name    applicationId  permission C2D MESSAGE   gt   lt permission     android name    applicationId  permission C2D MESSAGE      android protectionLevel  signature   gt    You can inspect the modified AndroidManifest xml file within the apk using aapt l -a app-debug apk to ensure the placeholder was properly applied  If you use various product flavors  I m sure you can apply a variation of this method to suit your needs

User · Answer

None of the above worked for me  My app was working fine in previous than Lollipop  But when I tested it on Lollipop the above error came up  It refused to install  I didn t have any previous versions installed so all the above solutions are invalid in my case  But thanks to this SO solution now it is running fine  Just like most developers I followed Google s misleading tutorial and I added the permissions by copy and paste like this    lt uses-permission android name  com google android c2dm permission RECEIVE    gt   lt permission android name  com google android permission C2D MESSAGE               android protectionLevel  signature    gt    This would work with older versions  lt  Lollipop  So now I changed to    lt uses-permission android name  com mycompany myappname c2dm permission RECEIVE    gt   lt permission android name  com mycompany myappname permission C2D MESSAGE               android protectionLevel  signature    gt

User · Answer

I ve found a solution that works for me   In My Device  Nexus 7  Android 5 0  Lollipop I follow these steps   After Uninstalling App You will find App Name under Apps List of the Downloaded tab     Go to Settings  Apps  At the bottom of the list  you will find YourApp with a  NOT INSTALLED  Tag  Open  Click on OptionMenu and Select  Uninstall for all Users    After these steps  I successfully install the new app and it s running well

User · Answer

In my case I was using a third party library  i e  vendor  and the library comes with a sample app which I already had install on my device  So that sample app was now conflicting each time I try to install my own app implementing the library  So I just uninstalled the vendor s sample app and it works afterwards

User · Answer

In my case I received following error     Installation error  INSTALL FAILED DUPLICATE PERMISSION   perm com map permission MAPS RECEIVE pkg com abc Firstapp   When I was trying to install the app which have package name com abc Secondapp  Here point was that app with package name com abc Firstapp was already installed in my application   I resolved this error by uninstalling the application with package name com abc Firstapp and then installing the application with package name com abc Secondapp  I hope this will help someone while testing

User · Answer

Remove any  Hard Coded  reference of your package name  from your manifest file    This is best practice even if you don t using productFlavors   For example  if your manifest contains    lt uses-permission android name  com google android c2dm permission RECEIVE   gt   lt uses-permission android name  com yourpackage name permission C2D MESSAGE   gt    lt permission     android name  com yourpackage name permission C2D MESSAGE      android protectionLevel  signature   gt   lt permission     android name  com yourpackage name permission MAPS RECEIVE      android protectionLevel  signature   gt    Changed it to    lt uses-permission android name  com google android c2dm permission RECEIVE   gt   lt uses-permission android name    applicationId  permission C2D MESSAGE   gt    lt permission     android name    applicationId  permission C2D MESSAGE      android protectionLevel  signature   gt   lt permission     android name    applicationId  permission MAPS RECEIVE      android protectionLevel  signature   gt    Then  in your module gradle file  set your relevant applicationId   signingConfigs       stage           storeFile file  keystore stage keystore           storePassword  android          keyAlias  androiddebugkey          keyPassword  android            production           storeFile file  keystore playstore keystore           storePassword store password         keyAlias key alias         keyPassword key password          productFlavors       staging           signingConfig signingConfigs staging         applicationId defaultConfig applicationId     staging          versionName defaultConfig versionName    -staging             production           signingConfig signingConfigs production           You can follow this tutorial for more info

User · Answer

Installing an application in OS 5 0 i get this message   INSTALL FAILED DUPLICATE PERMISSION perm com myapp permission C2D MESSAGE pkg com myapp   There  s no duplicated packages  and we can solve this issue uninstalling manually the old application or using the adb   adb uninstall com yourpackage

User · Answer

Previously it used to say that an app with different signature is found on device  When installing from IDE it would also ask do you want to uninstall it   But I think from Android 5 0 they have changed the reason for uninstallation  It does not happen if you are installing app with the same signature

User · Answer

Remove    lt uses-permission android name    applicationId  permission C2D MESSAGE   gt   lt permission     android name    applicationId  permission C2D MESSAGE      android protectionLevel  signature   gt    Run App    Then Add the permisson again and Run App   Ready

User · Answer

try to uninstall the app with adb   adb uninstall com yourpackage

User · Answer

CommonsWare is right  but in my opinion this is a  bug poor way to say   The apk installed on the device is signed with a different certificate then the new one you are trying to install    This is probably a new bug since in the past it used to ask whether or not to uninstall the app from the device due to wrong certificate   The solution as painful as it may be would be to uninstall the app it manually   Also what we ve done for the sake of team development  we added the debug keystore to our repository  and point gradle to use it like so   android               signingConfigs           debug               storeFile file     certificates debug keystore                                 buildTypes           debug               signingConfig signingConfigs debug                              And now when passing devices between team members  we all use the same debug certificate  so there is no issue

User · Answer

In my case  I had several applications installed having the same domain name in the package name as follows    com mypackage app1 com mypackage app2 com mypackage app3        I had to uninstall all the apps having similar package names and reinstall them again in order to get rid of the problem    To find all package names from the device I used the following    adb shell pm list packages   Then I grabbed the packages that match my package name that I am looking for    dumpsys   grep -A18  Package   com mypackage      Then uninstalled all the apps having that domain    uninstall com mypackage app1 uninstall com mypackage app2 uninstall com mypackage app3       You can also uninstall the applications using the Settings app  Go to the Settings - gt  Apps - gt  Find the app - gt  Uninstall  Hope that helps someone having the same problem as me

User · Answer

See this link it said that it will work when they are signed by the same key  The release key and the debug key are not the same   So do it   buildTypes           release               minifyEnabled true             signingConfig signingConfigs release  signing by the same key             proguardFiles getDefaultProguardFile  proguard-android txt     proguard-android txt                     debug               applicationIdSuffix   debug              debuggable true             signingConfig signingConfigs release  signing by the same key                    signingConfigs           release               storeFile file       key  jks               storePassword  key                  keyAlias  key                  keyPassword  key

User · Answer

If you have a different flavour of the app  try uninstalling that first  This helped me when I had the same issue

User · Answer

In your AndroidManifest xml file  change your specially declared permissions  names  for example    lt  -- Creates a custom permission so only this app can receive its messages  NOTE  APP PACKAGE permission C2D MESSAGE -- gt      lt permission android name  com myapp permission C2D MESSAGE  android protectionLevel  signature    gt   lt uses-permission android name  com myapp permission C2D MESSAGE    gt       lt  -- END GCM -- gt    to this    lt  -- Creates a custom permission so only this app can receive its messages  NOTE  APP PACKAGE permission C2D MESSAGE -- gt      lt permission android name  com myapprocks permission C2D MESSAGE   android protectionLevel  signature    gt   lt uses-permission android name  com myapprocks permission C2D MESSAGE    gt       lt  -- END GCM -- gt    com myapprocks this part solves the conflict with your other app

User · Answer

I uninstalled previous version  It worked for me

User · Answer

For making the application  amp  its multiple instance you can directly add this line then you can able to install the multiple application with same package name every time just modify the application id  Example    application id   XXXX 123  Old or existing one which is installed in phone  Now make application id as   XXX 1234 and install the app  Format   lt uses-permission android name  quot   applicationId  permission C2D MESSAGE quot   gt   lt permission     android name  quot   applicationId  permission C2D MESSAGE quot      android protectionLevel  quot signature quot   gt

User · Answer

replace below lines    lt permission android name  com myapp permission C2D MESSAGE  android protectionLevel  signature    gt   lt uses-permission android name  com myapp permission C2D MESSAGE   android protectionLevel  signature    gt

User · Answer

I had the same problem with a custom signature permission on Android-21 and solved it by making sure I was doing a complete uninstall    This is an edge case that occurs when    An application defines a custom permission using signature level security You attempt to update the installed app with a version signed with a different key The test device is running Android 21 or newer with support for multiple users   Command line example  Here is a command-line transcript that demonstrates the issue and how to solve it  At this point a debug version is installed and I am trying to install a production version signed with the release key     This fails because the debug version defines the custom permission signed with a different key    root localhost svn-android-apps     androidbuildscripts my-adb-install Example release 920 KB s  2211982 bytes in 2 347s          pkg   data local tmp Example-release apk Failure  INSTALL FAILED DUPLICATE PERMISSION perm com example android example PERMISSION EXAMPLE PLUGIN pkg com example android example     I use uninstall -k because apparently that is similar to uninstalling as a user   by dragging the app out of the app tray    root localhost svn-android-apps    android-sdk-linux platform-tools adb uninstall -k com example android example The -k option uninstalls the application while retaining the data cache  At the moment  there is no way to remove the remaining data  You will have to reinstall the application with the same signature  and fully uninstall it  If you truly wish to continue  execute  adb shell pm uninstall -k com example android example     Let s go ahead and do that    root localhost svn-android-apps    android-sdk-linux platform-tools adb shell pm uninstall -k com example android example Success    This fails again because the custom permission apparently is part of the data cache   that was not uninstalled    root localhost svn-android-apps     androidbuildscripts my-adb-install Example release 912 KB s  2211982 bytes in 2 367s          pkg   data local tmp Example-release apk Failure  INSTALL FAILED DUPLICATE PERMISSION perm com example android example PERMISSION EXAMPLE PLUGIN pkg com example android example     In spite of the warning above  simply doing a full uninstall at this point turned out to    work  for me     root localhost svn-android-apps    android-sdk-linux platform-tools adb uninstall com example android example Success    Release version now successfully installs    root localhost svn-android-apps     androidbuildscripts my-adb-install Example release 898 KB s  2211982 bytes in 2 405s          pkg   data local tmp Example-release apk Success   root localhost svn-android-apps      Eclipse example  Going in the opposite direction  trying to install a debug build from Eclipse when a release build is already installed   I get the following dialog     If you just answer yes at this point the install will succeed   Device example  As pointed out in another answer  you can also go to an app info page in the device settings  click the overflow menu  and select  Uninstall for all users  to prevent this error

User · Answer

I restarted my phone after uninstalling the app and it worked

User · Answer

I encountered the same problem with a nexus 5 Android Lollipop 5 0 1    Installation error  INSTALL FAILED DUPLICATE PERMISSION perm com android    pkg com android      And in my case I couldn t  fix this problem uninstalling the app because it was an android app  but I had to change my app custom permissions name in manifest because they were the same as an android app  which I could not uninstall or do any change    Hope this helps somebody

User · Answer

In Android 5  check your settings -  apps  Instead of deleting for just the active user  since android 5 can have multiple users and my phone had a guest user  tap on the accessory button in the top right corner of the action toolbar and choose  uninstall for all users   It appears that in Android 5 when you just uninstall from launcher you only uninstall the app for the active user    The app is still on the device   This had me dazzled to since I was trying to install a release version  didn t work so I thought ow right must be because I still have the debug version installed  uninstalled the app  But than still couldn t install   First clue was a record in the app list of the uninstalled app with the message next to it that it was uninstalled  image

User · Answer

While giving this error it will clearly mention the package name of the app because of which the permission was denied  And just uninstalling the application will not solve the problem  In order to solve problem we need to do the following step    Go to settings  Go to app  Go to downloaded app list  You can see the uninstalled application in the list  Click on the application  go to more option  Click on uninstall for all users options   Problem solved  D

[android] INSTALL_FAILED_DUPLICATE_PERMISSION... C2D_MESSAGE

Examples related to android

Examples related to google-cloud-messaging

Examples related to android-notifications

Examples related to android-5.0-lollipop