Sometimes less than 1 promille of the database upgrades of my app fail. This in itself would be annoying, but what is worse that I don't get to know about it .. usually.
I installed an exception handler in my Application, but it seems that the ContentProvider get initialized before the Application and the ContentProvider needs the db upgrade that subsequently fails and gets not reported, because the Application has not been initialized yet. Any idea if there is a fixed order in which what is started?
-- 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
