Error updating app on Google play store after introducing new google policy

Question

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         


        

Answer 1

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!

Answer 2

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.

Answer 3

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/)

Answer 4

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.

Answer 5

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.

Answer 6

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.