I’m sending my app to revise right now, hopefully i can tell you something within two days
2 Likes
i a gree
in the requested permissions of the relise I don’t find “BACK_GROUND_LOCATION” so I think it’s solved thanks
1 Like
Hi, unfortunatly i experienced the same problem again:
This is the answer from Google Play Store:
Issue with your app
Unclear feature description
We were unable to identify the feature that requires access to location in the background based on the declaration you submitted. Please resubmit a declaration with a clear description or additional information regarding the one feature that requires access to location in the background. Even if your app has multiple features that require access to location in the background, please only select one feature and resubmit your declaration form.
When selecting one feature, please note the following:
Your selected feature should deliver clear value to the user and be important to the core functionality, or main purpose of the app. Without this core feature, the app is “broken” or rendered unusable.
You should also consider if users would expect the app to access their location in the background, and if you can deliver the same experience without accessing location in the background.
Please note that access to location in the background solely for the purpose of ads will be denied.
Action required: File an exception and roll out a submission (see below), or submit a compliant update
We realize that compliance with this policy may require substantial work for some developers, so we are offering an extended timeline to make any necessary changes. You will have until the following dates to bring your app into full compliance (or to remove access to location in the background if your app does not meet the necessary requirements):
Apps published on or before April 16, 2020- Submit a compliant version of your app by March 29, 2021.
Apps published after April 16, 2020 - Submit a compliant version of your app by January 18, 2021.
These dates are subject to change, and may be pushed back. Until then, you will also have the option to request an exception and roll out your latest submission, which will allow you to continue using location in the background without making changes. During this time, we recommend that you review the issue(s) identified above and start developing a compliant version of your app. If you’d like to become compliant now, we suggest that you review best practices for accessing location data and evaluate whether you really need access to location in the background.
Please review the Permissions policy, Location Permissions policy, and Help Center article for more information, then proceed with one of the following options:
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.
wei
December 2, 2020, 12:01am
103
Does your app use the location sensor/Map/BLE component? If not, can you DM about project link?
Wei
wei
December 2, 2020, 12:16am
105
Did you build and submit a new apk to the Google play store?
Wei
Yes I certanly did.
I’m 110% sure that’s the newest file and the latest I have downloaded from thunkable.
wei
December 2, 2020, 12:23am
107
I am sure there is no request of location from your app apk manifest. What did Google say when you submit a new APK to the play store?
Wei
1 Like
It sent my apk to review at 23:34, at 00:16 i received the mail from Google, the same mail i have quoted you few messages ago. A bit early, it has been such a quick response, if I can say; usually Play Store takes few hourse/days.
Nothing else.
1 Like
wei
December 2, 2020, 12:39am
109
Let’s wait to hear what others have to say.
Wei
1 Like
@wei I think it has been fixed. While I was uploading my APK, I didn’t receive any error regarding Background Location Access while earlier I was receiving such errors.
I can confirm it to you within 2-3 days.
2 Likes
Does it still ask for a location permission with a WebViewer component? Just wanted to be sure before we try it out to avoid confusion. Thanks
1 Like
@wei it would seem to have worked because if I go to the submission form in “Authorization declarations” relating to geolocation and try to see which relise have the problem, the one added after the fix is not there, so consequently it does not contain the request for the resource geolocation, it would automatically appear to be fixed.
I will confirm in 1/2 days
1 Like
No - it shouldn’t do this any more. Can you let us know if you encounter any issues?
Awesome, thanks @Jason_Priore !!
@maurizio.polverini89 - if you try download/update again now, does it work for you?
1 Like
Sure. As of now it is not showing the error while uploading. We will surely write to you again in case we face any issues.
A hearty thanks to the Thunkable team for the efforts put, and for the prompt solution.
1 Like
Hey everyone,
Just to close out this topic - the engineering team were able to get a fix out for this yesterday and everything seems to be working as expected again when publishing apps now.
Please leave a like here if it’s working for you and if any new issues arise, please create a new topic and @ me.
Thanks!
cc: @agha96mujm @Deluxe @bmh1974 @sinu.mathewj @isazaly @strazco @drted @prottomakers @roumak-coder , @aditya.paul , @dishanklz6pq , @amit.apte47 , @vinit932vj5xfp , @mashrupurvang199718t , @milanc , @nidhivsvijanrzhpph @vinit.salian1997kj6 @amit.apte47 @murtazag01235baora @emregoker @maurizio.polverini89 @ayushkar04027e4eba @dishanklz6pq @Jason_Priore
Also thanks to @maxb and @appspark.uk for helping out with troubleshooting and suggestions here too.
6 Likes
Hi , many of us are facing similar issue due to Google’s new location permission policy. 5 of my apps doesn’t need any sort of location access but the ACCESS_BACKGROUND_LOCATION permission is turned on in all the 5 APKs downloaded from Thunkable. Can we get some help?
I can’t upload to google play store due to this error why???
Your app has been rejected and wasn’t published due to this policy issue. If you submitted an update, the previous version of your app is still available on Google Play.
Please remove the background location permission requested and submit an update to your app. When declaring a feature for background location access, please note the following:
Your selected feature should deliver clear value to the user and be important to the cor…
I am having the same issue. How did u resolve?
@sinu.mathewj @youngachievers
Please see the post above:
3 Likes