Please keep in mind that a response from Google is taking longer than expected due to COVID. Your app does not include the `ACCESS_BACKGROUND_LOCATION` permission. Your app is blocked from release because of the "background location permission" warning. Fill in the required info for your account "Contact options", click email (or chat if you need a faster response)Ħ. "Confirm issue", click `Declare Location App Permissions`ĥ. "Let's get started", fill in `App update blocked by background location permission`ģ. The old way of contacting Google Play Developer Support through emailġ. But the community isn’t getting answered that fast. Try Tweeting them using Or try posting on their community forums, don’t mention security sensitive info.Try using Facebook Messenger to chat with them.If your app is getting rejected, use the contact or appeal options in that email instead.That leaves us with fewer options, here are some that might help: You can use this link to get in touch with Google Play Store support.Įdit, as mentioned, it looks like Google removed the Declare location app permissions option and the ability to directly email Google Play Developer Support. If your binary is still getting blocked, even after removing older binaries with the ACCESS_BACKGROUND_LOCATION permission, you need to contact Google. If you want to try that, make sure to change the name and the android.package in your app manifest to create a different app. You can also create a new app in Google Play Console to test if the binary is allowed. See this Stack Overflow thread for more info. If you uploaded a new binary, and double-checked that it doesn’t include that permission, remove the older binaries from the Google Play Console. You might have older binaries uploaded in the Google Play Console that uses background location permissions. Removing older binaries from Google Play Console Validate if the ACCESS_BACKGROUND_LOCATION is not listed, if it is remove this permission (see above).Run aapt2 d permissions path/to/app.apk.Check if you can use AAPT2 (see getting started).When you built a new APK, we can validate the included permissions with the AAPT2 tool. Build a new APK with Android Studio or CLI.Optionally, you can force-exclude this permission by adding tools:node="remove" (see the permissions docs).Check if your AndroidManifest.xml doesn’t include the ACCESS_BACKGROUND_LOCATION permission.Make sure your targetSdkVersion and compileSdkVersion target 29 or higher.Before this version, the background location is implied when using both coarse and fine location permissions. Google added the background location permission in this version. Build a new APK with expo build:android -type apk -release-channel permission-audit.įor bare workflow, make sure you target Android SDK 29.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |