My application is causing a force close somewhere but instead of getting a FATAL EXCEPTION with the usual (and very informative) stack trace in my LogCat, I only receive onl
this is going to be tedious, but i would single step through until it breaks with the debugger. then you can add a more general catch
catch(Exception e){ }
All exceptions extend from Exception so that may help you further diagnose you're problem.
One more idea, perhaps you're app is running up the device memory. The JVM could be killing you're app without telling you because of a JVM shutdown on memory error.