Location permission declaration needs to be updated even after removed permission - App Content - Reject Google Play Console

Solution :

1. First of all fill-out form of declaration for location permission (Any Sensitive permission used in previous rolled out APK version). This will fixed temporary error of App Content - Sensitive Permission Issue.

   In my scenario i have added no usage of background location In declaration and random youtube video link.

2. After permission declaration you can create/edit new release. Make sure before adding new release APK to console please analyse APK and make sure that that sensitive permission is not used again. (If you used that sensitive permission again than you need to add valid sensitive permission declaration in AppContent -> Sensitive Permission)

3. After Creating new release version you can roll out new release version from Release dashboard.

4. After Roll out go to App content -> Sensitive App Permissions -> click on Manage and Select No Radio Button and Save it.

5. ITS DONE. Your new release version app will be live soon!

I had the same problem - I didn't need anymore this permission but the APK in prod used this permission (and also some releases of some tests) so the console let me only explain why I needed this permission and didn't display the question if I do use this permission.

When I tried to add new tests I was always rejected because I didn't have a good reason why I needed the background access permission. If you don't need this permission anymore: (I don't have the exact name of the sections, actions because I have a non-english language in Google Play Console)

I found a solution that worked for me: App Update is rejected from google play due to Background Location access (But I didn't use any background location Permission).

In App content -> Sensitive App Permissions -> click on Manage -> Click on Display APKs.... You will see all the APKs that use the background permission. Those APKs can be used in Tests or Production.In order to fix the problem you will need this list to be empty. APK from Test sections: For each test - search the source of the release (a release from a test of internal tests/closed tests...) Under the test section, click on Manage (even for suspended tests), click on New Release and add an empty release (without APK) click to examine the release.[Add a new empty release under the test/s that uses a release with an APK that requires the background access permission. Don't add new empty tests].

APK from Production: You will have to add a new release on Production that doesn't include the background permission.

Now you will see that no APK is displayed when clicking on Display APks... on Sensitive permission... Now when clicking on Manage (under Sensitive permission..) you will have a new question - if you do use the background access. Click on "No" and now you can add new Tests.

I had a similar problem when modifying an application in production that did not use the sensitive permission, but had it declared

The reason that the Play Store Console showed the application stuck in "under review" status was that it could not modify the permission statement, caused by having limited the scope of the app to a single country, limit that was different from the version that was in production

After being able to adjust the regional distribution to all countries, I was able to start the release of a new version that did not use sensitive permissions, with which the permission declaration form could now show me the correct question that had nothing to do with location in background ("Does your app access location in the background in APKs or app bundles targeting Android 9 or older?") according to the documentation in:

https://support.google.com/googleplay/android-developer/answer/9799150?hl=en#zippy=%2Chow-do-i-remove-location-in-the-background