On Fri, Dec 05, 2014 at 10:27:56PM -0500, Steve Gabrilowitz wrote: > You could try putting a try/catch block around the offending statement to > catch a generic exception, maybe finding out exactly what exception pops up > might give you a clue?
I tried that. The catch statement, which should have logged the error, became the new source of the force close. And logcat did not give ANY additional data. :-( I also tried deleting the database and re-creating it. It STILL shows up as much smaller than the copy in assets, but I'm still assuming Android quietly does some kind of compression on it. 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.
