Thanks for sharing the link. I wasn't aware of this bug report.
Yes both apps are mine, but even though they have the signature, some user
complain about this error. Maybe they installed the apps form different
sources, i.e. Amazon and Google Play.
cheers
Marten
Am Freitag, 20. Februar 2015 1
I'm seeing this with android:protectionLevel="normal" too.
Since Android doesn't grant permissions that had not been declared yet,
this forces the user to install apps declaring / using the permission in a
certain order.
This is a pain for the user, so the developer of one app that works with
Hi Marina,
we're using android:protectionLevel="dangerous" because that's what we
think is suitable for personal data like tasks. Also, it's what the
CalendarProvider uses for the permissions to read and write calendars.
At present the major issue is that some users get this error even though
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
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
5 matches
Mail list logo