Develop Reference

Problems with location permission on android [EXPO| REACT NATIVE]

I'm trying to update an app that has already been published on the PlayStore but is now being refused because GOOGLE informs that the app does not respect usage policies. I receive the following message:
- The app does not comply with the Location Permissions policy
Email with details send by google
After receiving this response from Google, I have already corrected my code, but the app continues to be refused.
Below are the actions I have already taken to try to resolve the issue:
When I received the lock for the first time, I made the requested corrections in the application code. The app currently requests the following permissions:
permissions on code
Below is the print of the permissions after uploading the .aab to the playstore:
enter image description here
Accessing the play store policy menu, I noticed that the privacy policy setting is linked to build number 29 but I'm already trying to send build 35.
This build 29 uses background localization, but I can't unlink it from the policy configuration tab or add another app version.
app settings in play store
wrong permissions in build 29
I've also reviewed the features that use localization in the code and everything is fine. Below screenshots of the code:
code snippet 1
code snippet 2
code snippet 3
I would like to know if anyone has had similar problems and can give me some guidance on how to solve it?

First thing, I noticed that you wrote "ACCCESS_COARSE_LOCATION" (with 3 C). I don't know if this is the error, but better spell it right.
Second thing, be sure that you declared that you DON'T use background location. To do that, go to your Google Play Console, select your app, then go to
App Content (it should be the last section on the left) -> API and sensitive authorizations -> Manage
then set "No" to the question regarding background location.
This is the screen you should see after these steps

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

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.

Solution :
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.
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)
After Creating new release version you can roll out new release version from Release dashboard.
After Roll out go to App content -> Sensitive App Permissions -> click on Manage and Select No Radio Button and Save it.
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

The issue is that an outdated APK/App bundle file was added to the Alpha/Beta testing phase (but never moved to production), and rather than correcting it, he added a new APK/App bundle to the live environment. The Alpha/Beta file is currently being reviewed rather than the new production file due to changes in how reviews are carried out by Google. In Google's denial, you can see the versionCode of the previous APK/App bundle.
The new APK/App bundle file should therefore be added to the same Alpha/Beta as the old one before being promoted to production. Once you have done that, go back to APP CONTENT and you will see there yes/no form. Issue is resolved.

Google Play - File an exception and roll out a submission

I have released a version of an application that collects background information and I received a notice from google play that it is rejected. Google has outlined next steps as either submitting a compliant update by Jan 1 2021 or requesting an exception. I am a bit confused about exactly what to do though as I don't understand what they mean by 'submit' app. Do I need to make another release once I either declare an exception or submit the declaration form filled out?
Option 1: File an exception and roll out a submission (without making changes)
During the extended timeline for compliance, you will be allowed to roll out your latest submission without making any changes by requesting a Location exception. Here’s how:
Sign in to your Play Console
Select your app.
Navigate to the Permissions Declaration Form.
To file an exception in the form, go to the question “Does your app meet the Location permissions policy?” and select “No, this app does not meet the Location permissions policy.”
Selecting this option will allow you to access location in the background in your latest submission, in any updates to your app, or when submitting a new app, until the dates mentioned above. For more information, please visit our Help Center.
Submit your app.
Option 2: Submit a compliant update
Once you’re ready to submit a compliant version of your app:
Make the necessary updates to address the issue(s) identified above.
If your app is not eligible to access location in the background or does not meet requirements for accessing location in the background, please remove the permission from your manifest and in-app functionality.
Double check that your app is compliant with all other Developer Program Policies.
Sign in to your Play Console and submit the update to your app.

Here is the solution
remove permission
and go to google play console
select app
select App content
select Sensitive app permissions
select manage
select No, this app does not meet the location permissions policy

How to submit the Facebook app for review?

I am working on an app that needs to update a Facebook user's status using a custom composer in an Android app. Also, I would like to get the user's videos to show them inside the app itself. I believe I'll need the following permissions to achieve the desired features.
publish_actions
user_videos
To get those permissions, I need to submit my app for review. I have prepared the required stuff for that such as, steps to reproduce and screencast of mobile app, to give an idea of the features working. Facebook also requires the APK to be uploaded along with the submission. But, the problem is I don't have the required permissions for now, so how will I demonstrate the exact feature up and running in the Android app? Without the APK, I won't get the app reviewed.
Is there any way to get the required permissions for some users, so that I'll be able to demonstrate in the screencast? Please help.
PS: I tried to add some Test Users but they don't seem working fine.

Follow these simple steps to submit.
1.Open your app in facebook console account.
2.Go to App Review,in app Review click the button Start a submission.
3.On Left List of Items will be displayed.
4.Select Items for Review
5.You have to Add Notes for Each Permission(Add the text to explain why u need that particular permission or add a video clip or
Screenshots.
*NOTE*:--make your note in such a way that they can understand your requirement clearly,otherwise they are not going to approve it.
6.AtLast Press the Save Button for submission.
Guys You need to wait for minimum 1-2 days to get approval.
You will get Alert in the Alert Tab on Facebook Console account of your app,
once you will get the approval,then good to go.
Hope it will help someone.

Google Play Developer Console - An unexpected error occurred. Please try again later

I'm trying to reply to users who have just provided ratings, however, from past 2 weeks I'm facing this error and I'm unable to successfully open the link.
Are you facing this error or I'm the only one that is targeted by Google ?
Help me to provide users the required support!

After July 2020 google has updated the play console and redirected on this url If you have not redirected automatically to the above link then manually open this link.

Make sure you only have a google account started in the browser

Google Developers Testing New Play Console In Beta Version
Visit
https://play.google.com/console/developers
Then sign in From Your Account
Use The New Play Console :)

I encountered this error.
An unexpected error has occurred. Please try again later. (7)
The message here is obviously unhelpful. I contacted Google Play support about it and this is their response:
Due to some updates, only authorized users with the access of "Edit store listing, pricing & distribution" are able to edit content ratings page.
If you are the account owner, you can grant user permissions either at the account level or at the individual app level. To add a user at the app level, please follow these steps:
1. Sign in to your Play Console.
2. On the left menu, click Settings > Developer account > Users & permissions.
2.a. To add a new user, click “Invite new user” and type in the user’s email address.
2.b. To update permissions for an existing user, click the gear icon on the right and select "Change permissions."
3. Don't choose a predefined role from the "Role" drop-down.
4. Instead, add your app to the per-app permissions table with the "Add an App" drop-down.
5. Check the boxes in the appropriate column to add user permissions to specific apps.
5.a. For full functionality, some permissions need to be set to "Global." For more information, review the permission definitions table.
6. Click Send Invitation.
TL;DR: You need Edit store listing, pricing & distribution permissions on the app.

For me I had to go to the console -> Store Presence -> Pricing & Distribution -> Click on Country -> REFRESH EXCHANGE RATES -> Save. Than Complete the Content rating and it is now saved.

From July, 2020
Try the new link for Google Play Console
https://play.google.com/console

This was happening for me due to using another google account on chrome than the default. Using an incognito browser fixed the issue for me.

I logged in using InCognito mode and it worked