Some users of my apps also reported same issue, also same exception in the log.
What you can do is: Uninstall your app, power off, power on. if that doesn't work and the phone is rooted, ask the user to clean the app cache, and not install app on SDCard. That resolved all these kind of open database and file corruption issues. Walter On Apr 9, 12:46 pm, Mariano Kamp <mariano.k...@gmail.com> wrote: > > Mariano Kamp wrote: > > > I could ask the people with custom ROMs to check if the db-file is still > > > there. > > > Or add your own exception handler for this, do some experiments, and > > then send the results to yourself via whatever mechanism you're using to > > get the stack trace. > > That's a good idea, but it will take some time to deploy. As I haven't > gotten any other feedback I will still do that then. > > > FWIW, I have not run into this problem as an end user. > > No, me neither. -- 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 To unsubscribe, reply using "remove me" as the subject.
