This issue occurs when an app is trying to redeclare an existing permission, with error message
INSTALL_FAILED_DUPLICATE_PERMISSION. For the solution, just skip over to the "Solution" part.
logcat tells me there's a conflict with redeclaring permissions during installation (in my case, Amazon is trying to redeclare getui.permission.GetuiService, which is already owned by Camera 360)
10-25 08:06:37.805 749 824 W PackageManager: Package com.tencent.mm attempting to redeclare permission com.google.android.c2dm.permission.SEND already owned by com.google.android.gsf 10-25 08:06:37.926 4812 4812 D Finsky :  PackageInstallerImpl.cancelSession: Canceling session 121130466 for com.tencent.mm 10-25 08:06:37.926 4812 4812 E Finsky :  PackageInstallerImpl.handleCommitCallback: Error -505 while installing com.tencent.mm: INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.tencent.mm attempting to redeclare permission com.google.android.c2dm.permission.SEND already owned by com.google.android.gsf 10-25 08:06:37.926 4812 4812 W Finsky :  4.installFailed: Install failure of com.tencent.mm: -505 null 10-25 08:06:37.933 749 749 D ZenLog : intercepted: 0|com.android.vending|-973170826|null|10017,!priority 10-25 08:06:37.933 749 749 V NotificationService: pkg=com.android.vending canInterrupt=false intercept=true 10-25 08:06:37.964 4812 4812 D Finsky :  InstallerTask.cancelCleanup: Cancel running installation of com.tencent.mm
Currently, there is no official fix by Google, and most possibly, it's the app developer's responsible to fix it.
In our case, we were building an app based on our Library using Google Maps V2. The v2.API_KEY was assigned to the apps namespace. We assigned the MAPS_RECEIVE to our libraries namespace. This worked fine before L and was one less thing for our builders to worry about. Now we realize that we probably should have been assigning the permission & uses-permission name to the apps namespace. With the permissions pointing at our library name space, we get the "-505" when installing more than one of our apps.
However, there are some proposed solutions for consumer side: uninstall the bugged apps from Guest account,
Hey guys, I've found the issue with "INSTALL_FAILED_DUPLICATE_PERMISSION". If you have Android 5.0 and multi user enabled, check if you have the app that is causing problems in your "Guest" account and uninstall it. Then go back to your main user and try installing the app again. It worked for me! Hope Google fix this with multiple accounts.
or uninstall the bugged apps using
adb or 3rd-party apps,
° It will probably (not definitely) work if you uninstall the app, which you have to do via ADB (for those sufficiently technically savvy), and then reinstall from the Play Store. However, I don't know if this means that you'll lose all your settings and data for the app.
- Install app: https://play.google.com/store/apps/details?id=com.funtrigger.appinstaller&hl=pl and launch it.
- Select your bugged app from list and uninstall.
- Now you should install your app in proper way.