And no, sharedUserId doesn't mean the apps share the same files. On Feb 24, 12:31 am, "Michael ." <mish...@gmail.com> wrote: > I'm really not understanding how to implement shareduserid > > My understanding is that: > > *By default, Android assigns each application its own unique user ID. > However, if this attribute is set to the same value for two or more > applications, they will all share the same ID — provided that they are > also signed by the same certificate.* > > ok, so I understand I think theoretically how it should work at > runtime with release apps. Both apps set the same shareduserid in > their manifest files and are signed with the same certificate... and > then I should be able to read the same files and properties with both > apps. > > But I have not gotten to that stage yet.. > > I'm still testing in the IDE... so this is what I've done: > > - set shareduserid to same value in both apps manifests > - set debuggable to true in both apps manifests > > But I have problems even making an app run correctly... > > if I remove shareduserid.. my App A will run correctly... read and set > some preferences... on startup > > but if I set a shareduserid... App A will pop up a logcat window with > a lot of read in it.. seems there are problems writing files... > setting properties... this kind of thing. > > Does anyone know what is going on? And what must I do to get App A to > run corrrectly? (i.e. to run the same way it runs when the > shareduserid is removed)
-- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
