Hmm, I make heavy use of the DB and this would not pose any kind of problem for me. I can't imagine that it would pose a problem for you either Zsolt. If it did it means that any of your users that chooses not to upgrade, would break on upgrade + 1.
One of the things I really like about Android is the way that the SQLiteOpenHelper has been structured to assume that DB changes are a normal part of versioning. I find it very easy to handle micro versioning of the DB using that facility. #onUpgrade gives you oldVersion and newVersion and let's you choose what DDL gets applied. By pulling an APK from the Market and at some subsequent point publishing version X+1 just means that the code in SQLiteOpenHelper just needs to handle DB upgrades from X-1 to X+1 as well as from X to X +1. If your code can't handle that then IMHO its pretty fragile and not well suited to the rolling upgrades common to the Android platform. But back to question at hand, if Reactivate was only for those APKs up until you clicked on the publish or save button then why is it available for older APKs. Ie ones that have been long since published and deactivated? William On Oct 28, 3:55 pm, Zsolt Vasvari <zvasv...@gmail.com> wrote: > Maybe not in your app, but definetely in my app there would be issues. > > I use an SQLite database that I sometimes "upgrade" with new columns/ > tables as I add features to my app. > > Let's say I roll back an update, but the user's database will not be > rolled back. Then I release a fixed version that will again try > updating the user's database by adding those tables/columns. A recipe > for a maintenance nightmare. > > As I said, this may not be an issue for the flashlight apps out there, > but for any serious app, this could be a very big problem. > > On Oct 28, 1:45 pm, William Ferguson <william.ferguson...@gmail.com> > wrote: > > > > > > > > > I would have expected that if I rolled back to version X-1 in the > > console that users that had already updated to version X would remain > > there and not be prompted to rollback (nor be given the option to > > "update" to the older version). All users now going to the console > > would see version X-1 as latest. > > > No forward compatibility issues. > > Just a means of pulling a bad release from further distribution. > > > William > > > On Oct 28, 12:27 pm, Zsolt Vasvari <zvasv...@gmail.com> wrote: > > > > I bet if you never pushed the "Publish" or the "Save" button, you can > > > reactivate an older APK. > > > > But once you publish, a user might have a newer version of the app on > > > their phone than what's available on the Market. Then you update your > > > app again, essentially forkiing your app. This can become a huge > > > versioning nightmare, especially for more complex apps, and I am not > > > surprised it's not supported. > > > > On Oct 28, 9:18 am, William Ferguson <william.ferguson...@gmail.com> > > > wrote: > > > > > Not suggesting you could or should roll back what the user has > > > > installed. > > > > But would like to withdraw a bad APK so other users don't install it. > > > > > But as has been pointed out this is not possible without loading up > > > > another APK with a higher version nr than any previous APKs. > > > > > On Oct 28, 1:13 am, Zsolt Vasvari <zvasv...@gmail.com> wrote: > > > > > > This has always been this way, and it makes sense as you cannot "roll > > > > > back"what the user has installed. > > > > > > On Oct 27, 11:08 pm, William Ferguson <william.ferguson...@gmail.com> > > > > > wrote: > > > > > > > I had exactly the same situation tonight. > > > > > > It has to be a Market Console bug, otherwise what is the value of > > > > > > the > > > > > > reactivate button. > > > > > > > On Oct 27, 3:40 pm, Dusk Jockeys Android Apps > > > > > > <duskjock...@gmail.com> > > > > > > wrote: > > > > > > > > Before I waste my time by asking Market Support, who as we all > > > > > > > know > > > > > > > are about as useful as a chocolate teapot, has anyone managed to > > > > > > > successfully re-activate a previous APK in the Developer Console? > > > > > > > > I had a situation where I made an update last night, quickly > > > > > > > realised > > > > > > > there was a bug and wanted to rollback to the previous version. > > > > > > > But I > > > > > > > was unable to. When I deactivated the new one and tried to > > > > > > > reactivate > > > > > > > the older one it wouldn't let me, because the older one's Version > > > > > > > Number was lower than the current one. Well, yes, obviously. > > > > > > > > In the end, I had to recompile my previous version with a newer > > > > > > > version number, and release that as an "update". Mental. > > > > > > > > What is the point of a re-activate button that doesnt let you re- > > > > > > > activate? Or am I missing something?- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - -- 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
