Hi! I'm not sure how to help, because've only met this problem when there are several users set on a device.
If I install my app directly from Eclipse with my debug certificates, then uninstall the app and try to install a production copy, made with the release certificate, I've got the same error message INSTALL_FAILED_DUPLICATE_PERMISSION. Until I uninstall the app in every user by hand, I can't install the new one. At least in your case the error message makes sense :) When I was trying to understand that error message, I've read that it affected permissions with android:protectionLevel declared as "signature". Are you using that? Can you change it to "normal" without affecting your business model? Marina On Wed, Feb 18, 2015 at 11:58 AM, Marten Gajda <[email protected]> wrote: > Hi all, > > we've some problems with Android 5. There seems to be a new policy that > requires two apps that define the same permissions to be signed by the same > key. Otherwise you can't install the app getting the error > INSTALL_FAILED_DUPLICATE_PERMISSION. > This is very annoying and I'd like to know that the suggested > solution/workaround to this is. > > We have an Open Source task app that provides access to the tasks via a > ContentProvider. The concept pretty much equals the CalendarProvider. We > also have a (not yet Open Source) sync app that can sync to this task app > (or its ContentProvider). > The problem is that (in contrast to the CalendarProvider) our users usually > install the sync app first. That means the permissions of the task app are > not known when the sync app is installed. So they are not granted > automatically when the task app is installed afterwards. > > Until Android 5 the solution was to define the same permissions in the sync > app. But that doesn't work any more in some cases. If the user compiles the > task app himself he can not use our sync app at the same time, because they > are not signed by the same key. > > How can we achieve that we protect access to the task ContentProvider by > permissions still allowing them to use a self compiled version? > > Even if both apps are signed by the same key it doesn't seem to work in some > cases (does Android 5 also require both apps to be from the same source?) > > A similar issue exists when another developer tries to build a sync app that > can sync to our task app. He can not add the same permissions, because he > can't use the same signing key. But if he can't add the same permission > definition his app won't get the permission if it's installed before the > task app is installed. > > What's the solution of this mess? > > thanks > > Marten > > -- > Marten Gajda > Schandauer Straße 34 > 01309 Dresden > Germany > > tel: +49 177 4427167 > email: [email protected] > twitter: twitter.com/dmfs_org > > VAT Reg. No.: DE269072391 > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > --- You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
