I recommend people avoid shared user IDs. It is a hole you can never escape once you are in it.
It is true that you can't disable the components of another app that has a different uid. However, you could have a broadcast receiver in the other app that when invoked disables the appropriate component in that app. So the main app can just send a broadcast to the other app to disable its component. If you want to be secure, you can define a signature-only permission that the sender must hold. (Your .apks of course are good being signed with the same cert.) On Thu, Aug 18, 2011 at 12:23 AM, Jeremy Lakeman <[email protected]>wrote: > If they are signed by the same key, both applications should be able to use > the same user id, data folder and process space. > > I'm thinking of doing something similar, where the main application can > download and install additional apk's directly from our web site. But I > haven't got around to experimenting with it yet. > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
