I was under the impression that if you have an app installed without protection and then update to a version with protection you get force- closes.
I have no idea if it's been confirmed though, sorry. On Mar 31, 7:43 pm, rcs <rsar...@gmail.com> wrote: > Hello all... > > This morning, we updated our app on AM; this was our first update > since release of Android 1.1. > > In testing, on the emulator and with the signed .apk installed on our > handsets, everything appeared to be working fine; however, we uploaded > to AM, selected the new CopyProtection option, and published. Wertago > disappeared for about 30 minutes, and as soon as it reappeared, we > downloaded, installed, and started. Immediately upon starting, we got > a force close and were never able to get the app started at all. > > We've seen some discussions about similar app behavior experienced by > other developers, and there was mention of likely bugs in AM or in the > Copy Protection scheme. Has this been confirmed by Google, is there > any communication from them about a coming fix, or anything like that? > > Here's a little detail about what we gather from the logcat output. > Our app appears to fail upon attempting to open/create the database; > the relevant line is: > > tmpDatabase = instance.openOrCreateDatabase(SEARCH_DATABASE_NAME, > Context.MODE_PRIVATE, null); > > which throws the sqlite3_open_v2 error. > > Any information, or even just commiseration, would be appreciated. > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
