Wednesday, November 3, 2010

[android-developers] Re: SharedIDs

Hi Dianne,

> If you just need to share data, a content provider can work very well.  You
> can set permissions on the content provider to a signature-only permission
> you define so other apps can't access the data.
>
> I can't help much more without actually knowing what you are trying to do.

I have two separate projects that need to run as two separate
processes -
but they do share cache configuration files that need to be made
persistent
(I cannot just send the data between the two processes using IPC
sockets).
Unfortunately that is the requirement of this design .. I know it is
not ideal
but it is what it is ;)
I think you are right, content providers would be a potential soln so
I will look
into that.

> To use sharedUserId the two apps *must* be signed with the same cert, and if
> they aren't you will break.  You are right, you generally rely on using
> release signed .apks to ensure they are signed with the same cert...  you
> could play some games to ensure that development builds are signed with the
> same dev cert (by having all developers use it), but can't mix release and
> dev builds.

I agree on that!

Thanks

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate