On Fri, Dec 05, 2014 at 10:40:01PM -0500, Steve Gabrilowitz wrote: > Put a breakpoint in the catch clause and when it gets there examine the > exception - that's how I recently figured out a similiarly puzzling force > close.
Honestly, I don't even know how to do that. I've never run into a situation like this, where logcat says, "something happened...and it was here." I've always gotten more useful information either from it, or Eclipse warnings. The most frustrating thing about this stuff is that I'm trying to (hopefully) use this app to make enough money to pay for advertising so the games I'm working on (using AndEngine) will have a chance of making money to either directly make me enough money to get out from under Social (IN)Security Disability, which was forced on me by cancer #1, or to make money to add to my investing, which ultimately the same goal. The ironic part is, I can't afford to pay for advertising for the app I hope to make money to pay for advertising so my games can have a chance.... So when you combine that with this kind of stuff, where I'm completely at a loss, it makes for a really bad week. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > [email protected] ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
