Ok, well at least you admitted it !!!
In the future if you start getting a weird error, put try/catch blocks
with e.printStackTrace in the catch block to find what root cause is,
or use breakpoints and debugger. Add some logging code so that you can
tell when your code gets to various points ("Got to step1".. etc).
Basically don't treat your code as pristine, put stuff in there, muck
about.
try {
//code that's not working
} catch (Exception e) { //or even catch (Throwable t)
e.printStackTrace();
}
9 times out of 10 that will give you a ton of information.
Then when you find the error, you just take out all that junk. Use
source control if you want to see what you changed.
--
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
