I can almost think of no app that it is forwardly compatible. It is not trivial and, in most cases, not worth the effort to create a design that anticipates future changes.
On Oct 28, 11:45 am, Dusk Jockeys Android Apps <[email protected]> wrote: > Thanks, Zsolt, that's interesting. > But I don't really get it. > > Surely it is up to the developer to ensure that he is backwardly > compatible? > Or in this case, forwardly compatible? > > If I publish v16, then v17, I don't see why I can't then roll back to > v16 > if I'm comfortable that they are compatible. No different from me > making a v18, I need to ensure its compatible with all previous > versions, because fot example the user could still be on v14. > > In any case, there shouldn't be a functioning Reactivate button in > that scenario, as it doesn't do what it claims to do. > > On Oct 28, 10:27 am, Zsolt Vasvari <[email protected]> wrote: > > > > > I bet if you never pushed the "Publish" or 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 <[email protected]> > > 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 <[email protected]> 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 <[email protected]> > > > > 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 <[email protected]> > > > > > 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 [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
