Thanks for your response Mark. I came across some posts explaining how copy protected apps are run with different security/permission checks.
So I just upgraded my app and everything worked fine. To summarize what I learned: If you have a copy protected app, don't try to test an update by installing over the existing app an un-copy-protected update. Chad On Sep 29, 2:47 am, Mark Murphy <mmur...@commonsware.com> wrote: > Sheado wrote: > > So if I test by installing and upgrading via the browser only instead > > of the browser/market combination then things work out ok - I don't > > get the mismatched uid error: > > com.my.application.package.path has mismatched uid: 10031 on disk, > > 10046 in settings; read messages: > > If you are getting this with an ordinary application on an ordinary > (non-rooted/normal firmware) phone, that feels like a bug. In that case, > I would recommend writing up the problem over athttp://b.android.com. > > > Speaking of > > which, how are uid's generated - are we (as developers) supposed to > > know or care at this layer of abstraction? > > UIDs are generated by the system. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android App Developer Books:http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
