Did you activate copy protection on your app in the market? There have been force close issues reported when doing so. I do not know whether these have been resolved in the meantime or not. Did you increment the android:versionCode integer attribute in the manifest with you new version? (you should) Otherwise it might eventually have been a timing problem. I'm not sure all Google download data centers distribute a new version exactly from the moment on when it was uploaded.
-- http://deepdroid.com On Jun 3, 5:05 pm, chrispix <chris...@gmail.com> wrote: > We just released an update, and spent a considerable amount of time > trying to test. Once we released to the market, people started > complaining about it force closing. > > The only way we were able to make it force close was by installing our > app by the market. (why would that change our app?) vs. installing by > adb as a signed app? > > We also noticed that if you downloaded the app for the first time and > the newest version was 1.5.0, that the market forced 1.0 on you first, > then made you upgrade to 1.5.0, we resolved this by going to version > 2.0, but what other alternative is there to avoid that upgrade path? > > Chris. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
