But you can....
Both the new and the old publishing UIs have an "expert" ("detailed"?) mode
with a list of uploaded .apk's and there are buttons to deactivate / active
them as needed.
As for enabling some code only for release builds (or the opposite) --
Android build tools generate a BuildConfig.java which has a boolean
indicating debug vs. release builds.
Looks like there was an issue with that one, supposedly fixed now:
http://code.google.com/p/android/issues/detail?id=27940
Placing a special file somewhere on the memory card of development devices
and checking for its existence is another easy way to handle this that
doesn't require code changes when getting ready to release.
-- K
On Sunday, February 3, 2013 10:44:17 PM UTC+4, Jake Colman wrote:
>
>
> 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.
