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
Related
I am making a new test release for a new app and have filled out all requested info related to app content. Uploaded a new bundle and when I click review release, I get presented with errors of the style
Error Your background location permission declaration needs to be updated.
Error This release includes permissions that haven't been declared in Play Console. Go to Sensitive app permissions to update your permission declarations. Learn more
Error Your app cannot be published yet. Complete the steps listed on the Dashboard.
I would love to do this but there is nothing shown in the dashboard related to this, there were no form displayed during the process as stated by "The Permissions Declaration Form is displayed during the release process" and when I look deeper, I see nothing showing up under AppContent, as stated by "If you have an active app bundle that requires a Permissions Declaration, including releases on the Open, Closed, or Internal test tracks, an alert is displayed on the left menu under App Content"
My app does request location permissions in its manifest and uses it, but it seems play store wants me to specify this somewhere, but then again it doesn't let me.
I have not seen others with this issue, so either I am really confused, or this is a bug of sorts. Does anyone here know how to handle this?
You can fill the form in your App's Policy section.
Open Play console -> Select your App -> In the left panel at the bottom end there will be a Policy section. under that section select App content.
Here you will find the Sensitive Permission and API form in To do :
i'm having some problem on sending my app to production in play store
See, the first time i tried to send my app to production i received an email 3 days later with this:
After a recent review, we found that your app --- (---) is not
compliant with one or more of our Developer Program Policies. See
below for more information about your app’s status and how to correct
the issue.
Issue with your app
Issues with submitted video
We were unable to view the video you provided in your declaration.
Your video should show the in-app feature’s functionality showing
usage of location in the background, and how a user would trigger the
prominent disclosure, runtime permission (with user consent), and
feature in action.
Please check that your video is accessible, and/or modify your video
to demonstrate the declared feature that requires access to location
in the background, then resubmit your declaration form via the Play
Console. Affected APK(s): APK:7, APK:1
And i noticed this:
Your video should show the in-app feature’s functionality showing
usage of location in the background
Note: i created my app using react native and expo
So i realized that expo, by default, includes a lot of permissions in my app, hence, i decided to create a new build including only the permissions my app really needs. (Removing the background location)
ACCESS_FINE_LOCATION
ACCESS_COARSE_LOCATION
Then uploaded my app to play store and sent it to production on monday and today i received the same email saying my app was rejected by the same reason mentioned above.
After reviewing the email i read this: "Affected APK(s): APK:7, APK:1"
And my current app version is APK: 8 which means that i must edit all these versions
So the thing here is that i don't know how to change the code of the previous versions of my app.
What can i do to solve this? any suggestions
I think your video is not accessible or it is in private mode,
Google says for videos you can save it either you drive or youtube but when you put the video from your google drive you need to make it public other vises it will not able to access and then google will not allow to process it. your video should not have any copyright issues and also make the video that explains everything in a clear manner so that it would not creating any problem.
in my case I also got this type of alert then I follow the steps that google listed and make proper explainer video.
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
I have post an app-bundle on the Google Play Console few day ago, there found a mistake about Location permission, so I filled a form to explain why we doesn't use the location on my app.
But this morning, they send me an email to says my application was refused... with this email:
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:
1. Sign in to your Play Console
2. Select your app.
3. Navigate to the Permissions Declaration Form.
4. 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.
5. Submit your app.
Option 2: Submit a compliant update
Once you’re ready to submit a compliant version of your app:
1. 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.
2. Double check that your app is compliant with all other Developer Program Policies.
3. Sign in to your Play Console and submit the update to your app.
the problem is: I don't understand anything about the Google Play console, there is so much tab everything is complicated to understand.
How I'm suppose to do the Option 1 ? The Permissions Declaration Form is nowhere. The question “Does your app meet the Location permissions policy?” is nowhere !
So I have update some thing in my app, change the versionCode to 2 in my app.json, create the the app-bundle and then :
click on blue button "create a release" upload my new app-bundle. The error still here:
And I have 2 releases ! How I can delete one ?
I have also tried to delete my app but nothing about this. Did I have to create a new app with the same name but the new app-bundle ?
remove permission
<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION"/>
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
Working on trying out the market licensing service, and I'm running into a few problems with the sample application.
When I first ran the sample, I got an error saying that the application was not licensed. I linked my account to the simulator in order to get it to get the test response, and now I get an error saying "Application error: NOT_MARKET_MANAGED"
Does this mean that I have to upload the app to the market in order to test to see if it works?
Yes your app has to be on the market and if it already is, you have to have a version code number which is greater or equal than the one already published.
There may be another way. The comments on the sample's MainActivity read:
* The first thing you need to do is get your hands on your public key.
* Update the BASE64_PUBLIC_KEY constant below with your encoded public key,
* which you can find on the
* Edit Profile
* page of the Market publisher site.
* <p>
* Log in with the same account on your Cupcake (1.5) or higher phone or
* your FroYo (2.2) emulator with the Google add-ons installed. Change the
* test response on the Edit Profile page, press Save, and see how this
* application responds when you check your license.
And when you log into http://market.android.com/publish/editProfile you will see an option for changing the License Test Response:
Textually saying:
This License Test Response will be
sent to devices using #gmail.com
or the Test Accounts listed above for
applications you have uploaded to
Market. Additionally, this account
(but not the Test Accounts) will
receive this response for applications
that have not yet been uploaded to
Market.
If you click that selection list, you will see different options:
I guess all you have to do, for that initial sample LVL tutorial program, is change the response from Respond normally to LICENSED or any other setting you want to test.
UPDATE: It turns out that the above measure is insufficient. I still get the NOT_MARKET_MANAGED error. I guess that "Market Licensing Example" must be uploaded as previous answers suggested. Note, however, that it cannot be the debug version:
Oh, and you can't really upload that "Market Licensing Example" as is. You must at least change the name of the package:
I can see how Google's sample/example system could be improved to become more developer-friendly...
Weird. After uploading the application (just uploading and saving draft, not filling any other required fields), the "Market Licensing Example" stops issuing the NOT_MARKET_MANAGED error, despite the fact that clearly selected NOT_LICENSED. Instead it responds with the message Allow the user access. I also tried setting (for test & learning purposes) it to ERROR_SERVER_FAILURE but I get the same Allow the user access message.
Why?
You'd have thought "Saved Draft" would be just what this is for. Otherwise, you're selling an app which by definition cannot have been fully tested live.
Upload your app (.apk) to the market. The default state will be "Saved Draft", so it will not be be visible to the public, but you can still test the Licensing.
One other potential problem:
Make sure that the version you are testing/running has the same android:versionCode in the AndroidManifest.xml as the draft version in the market. If the versions differ, you will receive a NOT_MARKET_MANAGED error. (Apparently the RSA keypair used for license
checks is on a per-app/per-version basis.)
After a bit of a struggle I got this working. You can't use the LVL sample as is.
Here's what I did:
modify the project's package to something else (I used: lvl.test)
set MainActivity's BASE64_PUBLIC_KEY to the one in your Developer Console profile.
export the signed app
go to Developer Console and upload the app (create dummy images and give it a dummy name and description etc. just so that it saves and is listed as 'Unpublished')
install the exported app (from your filesystem) to your test device (i.e. adb install bin/path/to/your.apk)
on your device, open Android Market go to: Settings>Accounts> and select the one that corresponds to your Developer Console account
you can now select a static License Test Response in your Developer Console Profile and save it. When you run the LVL sample on your device the response will correspond to the one you picked!
From my experience, the app has to be published before LVL starts working, incl. static response testing. For me ERROR_NOT_MARKET_MANAGED went away only after publishing although the docs say you can Debug and test an application's licensing implementation, prior to
publishing the application.
Cool part is you can publish while only having alpha/beta builds -- the app won't really go live, only testing accounts will be able to use it.
When you're preparing for initial release, it may seem unnatural to hit Publish before you're completely sure everything is in working order (and the fact that you have to put in the description and screenshots before you can do that is even more alarming -- you'd think those are final touches) -- but you should, just make sure you've made a sane choice about the package name and whether the app is paid or free -- those things can't be changed after publishing. Publishing alone does not make the app public; unless you have a Production build don't worry about accidentally making an untested version go live.
This is related so it might help somebody:
I was testing on an Asus transformer and had to delete all non-developer accounts to get license testing to work (including my yahoo account). Once the other accounts were deleted all of the steps worked without a problem.
In my case I was getting because of Version code difference as..
Already published apk's version code = 2
and after some testing release new apk's I had set version code to 5
which was causing this error as version difference should be exact 1 with currently published apk..
same was applied with version name too..
If you already tried all the suggestions above try this:
I had the same response for a while and I could not figure out why this was the case. I read the entire documentation on App Licensing and still receiving the same annoying NOT_MARKET_MANAGED response code.
I was finally abe to resolve the problem by changing my applicationId in the AndroidManifest.xml file. I rewrote an app from scratch starting with a blank new project. The problem was that I did not use the exact correct applicationId. The problem was that the original application on the Google Play Store used a letter in upper case while I wrote all letters in lower case in the newly created project.
Since I corrected the applicationId to match 100% (including casing) I get the expected behavior of the licensing service.