> I have a period tracking program (P & O Tracker) that was working > without issues seemingly until the 1.5 update roll out. The code is > modified version of the NotePadV2 example code and uses its basic DB > functionality and overall structure. I have updated my SDK to 1.5 and > updated the ADT plugin to 0.9 as well. I am compiling the code on the > 1.1 base and running the program on an emulator running 1.5 and minSDK > is "2". > > On my emulator, I get zero problems and the program works as > expected. Unfortunately, many of my users are getting numerous "Force > Close" errors I am unable to reproduce. It seems that most of the > errors seem to come from a very uncomplicated startActivityForResult > call to the NoteEdit.class from the main class (NotePadV2) (same > structure as the NotePad example) and others seemingly when returning > from an activity to the main program. Everything is declared in the > manifest and is running without issues on my emulator running 1.5. > > Any help or ideas would be greatly appreciated as I am stumped on how > to determine the cause of the bug when I can't reproduce it locally.
I'm guessing you don't have an Android device. When you can afford it, nab one on eBay. It is always worthwhile to test on hardware whenever possible. In the interim, you could use Thread#uncaughtExceptionHandler to ensure you get control on any crashes. Then, post the stack trace to a Web service, or ask the user to email it to you as an attachment, or something. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
