Hi list,
I'd like to know if it's good practice to include a <permission>
definition used by a content provider in another app that uses the
content provider.
Here is the problem:
I have an existing app A that's already installed by a couple of users
and I have developed a new app B that has a content provider and custom
permissions for access control. Now I want to add optional support for
that new content provider in app A.
Just adding a <uses-permission> tag to app A won't work because all
users would have to install app B before they upgrade to the new app A.
Otherwise the new permission is not granted with the following message:
W/PackageManager( 201): Not granting permission
my.package.permission.PERMISSION_X to package my.other.package because
it was previously installed without
That's a huge problem because all users would have to uninstall and
reinstall the app to get it to work.
To solve this issue I've included the <permission> entry from app B in
app A. Now the permission is known even if app B is not installed. This
seems to fix the problem.
My question is: Is that guaranteed to work in future Android releases?
Is there a chance any future Android version will complain about the
duplicate definition of the permission?
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/groups/opt_out.
