Unable to deactivate APK accidentally uploaded to Prod
Asked Answered
U

2

29

My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.

In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?

I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.

Umeh answered 9/6, 2013 at 3:36 Comment(6)
I've got the same problem. It seems that once you upload a apk to prod, one always has to be there....seems like a bugScrewworm
For the record I did try to post the question on google forums a while ago but the moderator never accepted my question so never got posted. No idea how to even report the issue to google at this point.Umeh
Super frustrating. Same problem. We're supposed to release this week and I really wanted more beta testing, but to get new betas out, I need to re-publish prod. On the plus side, we got a few reviews. All 5 stars ;)Bentz
Possibly related: #19378070Skean
Did yo try un-publishing it? Or completely deleting it from alpha too and then uploading it again?Clap
This is a really ugly bug! or a really bad design and in that case, is worst !Donell
S
16

According to a Google customer service rep I contacted:

The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.

The Deactivate button is only useful for situations where you have multiple active APKs.

Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.

Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.

Savoyard answered 6/6, 2014 at 19:41 Comment(2)
As far as I know, nothing has changed. You can't deactive an already-uploaded APK, and you can't enable Beta testing without a published app.Savoyard
Actually I was able to enable a Beta testing without publishing a production APK, but after few months I uploaded a production one and now I'm unable to disable it.Toon
C
0

In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing

Citizenry answered 21/8, 2021 at 10:0 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.