Anyway, there was no risk of exposing the faulty version to the public since it took you just 5 minutes to upload a corrected version. It takes Google Play several hours until changes are committed.
On Sunday, February 3, 2013 12:44:17 PM UTC-6, Jake Colman wrote: > > >>>>> "T" == TreKing <[email protected] <javascript:>> writes: > > T> On Sat, Feb 2, 2013 at 8:08 PM, Jake Colman > <[email protected]<javascript:>> > wrote: > > >> I uploaded a new APK and discovered a bug a stupid oversight (I > >> forgot to turn off my debug flag). > >> > > T> You no longer have to manually change the debug flag. Just omit > T> it. When your run through Eclipse (using the debug certificate) > T> it's enabled by default. When you export for release, it's > T> disabled for you. > > This was an application-level debug flag that I use for things like > controlling whether the app should update my Flurry statistics. I > accidentally uploaded the debug version that did not invoke the Flurry > API. I needed to reset the flag and reupload the app. > > >> This got me thinking whether there was a better way to handle > >> this. What do I do if I upload a bad APK but need a few hours or > >> days to fix it? > >> > > T> Revert to your last good build in your version control (you do > T> have version control, right?), update version code, re-release. > > Yes to version control. Been a developer for many, many years and would > never work without it. In this instance I was able to quickly fix my > problem and upload a new version. I changed the version code but kept > the same version name. > > >> Is there a way to remove the latest APK and restore the APK that > >> was prior to it? > >> > > T> The developer console has this nifty notion of "active APK" and > T> buttons that read "set as active" (at least the old console > T> did). This might lure you into thinking that you can just push a > T> button and go back to a previous version. You actually can't and > T> this idea of "active APK" turns out to be utterly pointless and > T> begs the question of why it was ever even put there in the first > T> place. > > >> It see the "unpublish" option that I think that would remove the > >> entire app from the store. > >> > > T> Correct. You don't want to do that. > > Amazing. You would think that you could tell Google to ignore the > latest APK and reactivate the one before it. Since you cannot, the only > option is what you suggested - revert from version control and upload > yet another APK. > > Thanks. > > -- > Jake Colman -- Android Tinkerer > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
