On Mon, Mar 2, 2009 at 12:59 PM, Markus Junginger <mar...@junginger.biz> wrote: > > I wonder if it might be the same issue I ran into: > http://groups.google.com/group/android-developers/browse_thread/thread/c529496c831eded2/e0e8a406084f0a24 > http://code.google.com/p/android/issues/detail?id=2047
I can't say because I personally have never experienced the Force Close issues myself. I've deployed a test .APK on Market, upgraded it a few times and had no issues after updating. > > I have only free apps, but paid apps are always copy protected, right? They are supposed to be protected but I for one have disabled protection and am counting on the consciousness of my customers. I might turn protection on eventually if it won't cause any issues. > So, if apps break that rely on file / DB access, and the others don't > it could make sense. My paid and free apps are essentially the same. They don't touch files directly, but surely do touch files via SharedPreferences. I don't know if reading assets counts as well. The problem is that these Force Close issues are intermittent and I can't possibly reproduce them to see what's going on. I'm thinking of adding exception handling here and there, catch the unhandled exceptions, copy the stack trace to Clipboard and ask the users to e-mail the stacktrace (I don't want to do that from within the app because I don't want to increase the # of required permissions just for the sake of debugging). > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
