To update this thread. It appeared that there were some indeed valid force close issues, but even debugging on one phone did not cause it to fail until I did a factory reset on the phone. Then i was able to cause the force close.
Any thoughts? Chris On Jun 3, 10:05 am, chrispix <[email protected]> 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 [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 -~----------~----~----~----~------~----~------~--~---
