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

5,866

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!

Share:
5,866
Harsh Bhavsar
Author by

Harsh Bhavsar

Hello, I am Harsh Bhavsar. Having 4+ experience in mobile development and 1+ year of experience in flutter development. • In mobile development, I have worked with Image-Video Editing Apps, Survery Apps, Chat Apps, Location-Map based Apps, Various management Apps, BLE related Apps etc. About my area work in flutter. • I have worked with Flutter's UI/UX , Google Maps, Couchbase, Socket connection, Sync gateways, Localizations, Customised plateform specific plugins, plateform specfic codes/views, Firestores with flutter, Chat with XMPP(native Android) and openfire, FFmpeg for Image-Video processing etc. We have worked with MVC, BLoc and Flux design pattern/ state management based on project requirements.

Updated on December 27, 2022

Comments

  • Harsh Bhavsar
    Harsh Bhavsar over 1 year

    I am facing one problem regarding Android app new version publishing.

    Scenario :

    I uploaded initial flutter android app 2 month ago (Dec 2020) to google play store where we had accidentally added Location permission even with no use in code. (Just permission added in Android Manifest).

    Now we come up with new version of flutter android app and trying to create new Release version 1.0.2 it shows error while Submitting new release version of app.

    Error : Fix errors to rollout this release

    Issue is regarding used location permission in my initial app version which is live on play store

    Issue need to be fixed : Your background location permission declaration needs to be updated.

    In the App Content it showing error in Sensitive app permissions

    Note : In Sensitive app permission - Location Permission. It's not showing Manage Button instead there is a option to location permission declaration form.

    We don't want to use location permission now . so we removed location permissions and trying to upload new release version but still this location permission (Sensitive App permission) declaration showing error again and again.

  • Harsh Bhavsar
    Harsh Bhavsar about 3 years
    In App content -> Sensitive App Permissions : Manage button is not avaialable. Only Start button is visible where i need to declare usage of location permission.
  • rebecca
    rebecca about 3 years
    If you click on start what do you see? if you have the question if you do use the background access so click on "No" else check if you have a button of which APKs use this permission and see my answer how to remove them so that you will have the question if you do use the background access
  • Harsh Bhavsar
    Harsh Bhavsar about 3 years
    If i click start then its guiding me for my previous APK (which has permission) to declare purpose of location service. Even in my latest version apk there is no mentioned of location permission (As i analyzed APK before creating new release). There is no "NO" or "MANAGE" button in sensitive App permissions
  • Mr.Rao
    Mr.Rao about 3 years
    I am also having the same issue, please please update if you find a solution @HarshBhavsar
  • Harsh Bhavsar
    Harsh Bhavsar about 3 years
    Yes sure. I am in talk with google developer support. I will update if found any solution.
  • Harsh Bhavsar
    Harsh Bhavsar about 3 years
    @Mr.Rao Please try my solution it works for me. Check my answer.
  • Mr.Rao
    Mr.Rao about 3 years
    @HarshBhavsar, there is no radio button option now. there is no way to say NO.
  • Alex Rummel
    Alex Rummel almost 3 years
    This worked for me. Make sure in step 2 that you create a new release for every development track, not just your production track, and include your APK that doesn't require sensitive permissions for each release. It's absolutely extraordinary how useless Google support has been for me in resolving this issue