I directly pushed an app for release via managed publishing. Releasing it will cause chaos for our users as some endpoints are incorrect. How do I remove that build and replace it with a new one?
App has been approved in managed publishing, worried that even if I push a separate build to prod track, this bad app will also get released
Trying to delete the apk does not work as the delete buttons are missing. What can I do as the app really cannot go out in this state? Is there some way to remove the app?
Just don't release it.
That's one of the advantages of Managed publishing. It's not released released until you confirm it in the Managed Publishing section.
The bad version is not released. Just upload a newer version with a fix and push it to the release track just as you did with this version.
I want to publish a new version of my Android app on the Play store, but this time I turned on the Managed Publishing option. Till now, I did the following steps:
Selected Production option from the left menu and created a new release
Uploaded the bundle file and added release notes
Pressed Review release
My question is here: If I press Start rollout to production it won't auto-publish my new version, right? I will find these changes in Publishing Overview and I will be able to choose when to Publish these changes? I want to publish the new version of the app at a specific time and till then the review of the new version must be done.
I'm a bit confused because in this article https://support.google.com/googleplay/android-developer/answer/9859654?hl=en I couldn't find anything mentioned about Start rollout to Production button.
I am trying to upload a new version of my app on play store and getting following error while uploading:-
You can't edit this app until you create a new app release declaring sensitive permissions
I have tried removing CALL_PHONE permission that Google restricts in latest policy and my app does not contain any unadaptable data. But still getting same error.
If anyone faced the same issue. Please help me to resolve.
Thanks in Advance!!
If you are unable to submit a new version in any of the tracks, promote an older version from an Internal Track to Alpha or from Alpha to Beta or from Beta to Production. While doing this a Permission Declarations Form will show up querying Call Log and SMS permissions used in your app.
Once you have submitted this form and promoted an older version, you will be able to submit new versions of the app in all the tracks.
First find out how many active artifacts you have
Go to 'Release Management'->'Artifact library'
You must have more than one 'Active artifacts'
I have 3 active artifacts - 1 from production, 1 from beta and 1 from alpha (version 24, 6 and 4 --see below image)
Now you need to Upload a new APK(here apk with version code 25, and version name:3.0.2)
Go to 'App releases'->'Manage'->'Create Release'
Upload a new APK that you want to release ( here new APK with version code 25)
Retain the current version of APK (here version code 24)
Click ‘Add from library’ and Upload all active APKs(here apk with version code 6 and 4)
Now select Compliance status’ > check “No, this release does not meet the SMS and Call log” (see below image)
-Go to declaration section and select all (see below image)
-Click "Save" at the bottom of the page
-Now on same page, we need to deactivate (current market app (here apk with version code 24))
-Click "Save" again then select "Review"
-you'll be able to release a new version of APK by clicking "Start Roll Out" button.
(refer following link:https://www.reddit.com/r/androiddev/comments/ajddj6/play_store_console_you_cant_edit_this_app_until/efkqmx2/)
We fixed it first uploading the bundle in the Beta track and then promoting it to Production. Directly uploading it to Production produced the same error.
I found the solution after a lot of research. I was facing the same issue since yesterday. I had already removed both the sensitive permissions in my last release which were related to SMS and Call Logs and yet I was getting this warning.
The solution like #IvanF mentioned is to check if you have apps in any other tracks. You may do so by going to App Releases section in Play Console and check if you have any app under Open, Internal or Closed section. If yes, then you'd have to deactivate them first because that is where the problem lies. The way to deactivate apps in other sections is mentioned here -
https://www.reddit.com/r/androiddev/comments/ajddj6/play_store_console_you_cant_edit_this_app_until/eeye216/
Hope this helps.
I finally found the answer, I had non-compliant APKs in different tracks
if you had non-compliant APKs in different tracks, then that's what you should do
First: Go to App releases > Click Create Release in the track you need to update
Second: Upload the compliant APK, make sure to remove the sensitive permissions from this APK
Third: Retain the current APK
Fouth: Upload all active APKs from all tracks, you can do that by clicking on ADD FROM LIBRARY button above the upload section, make sure not to deactivate the applications, the declaration form will appear in the bottom of the page
Fifth: Fill the Declaration form by the following:
Compliance Status: Check No
Declarations check all
and save
Sixth: on the same page after the save, deactivate and remove all the non-compliant APKs and keep the new compliant APK
Seventh: Click save and review
and you are done!
I just followed these steps: source ([here][1])
Internal test: Create an internal test release to quickly distribute your app for internal testing and quality assurance checks.
Closed: Create a closed release to test pre-release versions of your app with a larger set of testers. Once you've tested with a smaller group of employees or trusted users, you can expand your test to an open release. On your App releases page, an Alpha track will be available as your initial closed test. If needed, you can also create and name additional closed tracks.
Open: Create an open release after you've tested a closed release. Your open release can include a wider range of users for testing, before your app goes live in production.
Production: When you create a production release, this version of your app is available to all users in the countries you've targeted.
I created a new android release in the Google Play Console. In the process I forgot to click the "Retain" button on the old APK. I didn't notice my mistake until I started to rollout the new release (which I immediately halted). I cannot find a way to edit the new rollout to retain the old APK from the current release. Is there way to fix this problem?
The reason I need to retain the old APK is that the new one does not support older SDKs.
You can do it by choosing Create Release, then Choose APK From Library, thus "republishing" your previous version.
To be honest, I did not think of it myself, it was suggested by Google Play support.
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.
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.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing