[Solved] Error Publishing my app on Google Play Store

[roumak-coder]

• Are you updating an existing app or publishing for the first time?
  Yes, publishing for the first time.
• Does your app contain a Webviewer?
  No
• Does your app use AdMob?
  No
• Does your app use the Map component?
  No
• Does your app use Push notification?
  No

My Invisible components are: Gyroscope and Sound.

[dishanklz6pq]

Hello @domhnallohanlon

We have been facing the same issue in multiple projects. Some do use web viewers, while many don’t use any of the mentioned components.

Really appreciate the team working on the issue.
To answer your remaining questions:

1. Some of them are updates to already existing apps, while most of them are being published for the first time
2. Some do use web viewers, while many don’t.
3. None of these use AdMob
4. None of these use the Map component.

Thank you for your prompt response. Do let us know further steps. In case if there is any external way to disable the location permission too, do let us know for the time being.

I have read somewhere that editing the manifest.xml file could help disable the permission, but not sure how that works. Any inputs on that too would be really appreciated for the time being. Thanks

[aditya.paul]

@domhnallohanlon I would request the thunkable team to please fix this error as soon as possible.

I have to publish my app before Friday for a project, in which I have put in a lot of effort. If I am not able to publish it, my hard work would be of no use.

I request Thunkable Team to fix this issue at the earliest or at least provide us with some solution.

[roumak-coder]

Hey, today while I checked the play console I saw that the app was published successfully I don’t know how (I didn’t even mailed back the location permission thing) but, It is published!!
Thanks for solving it!!

[Deluxe]

That is no solution. That is pure luck.

[aditya.paul]

True, I am still facing the same issue

[Jason_Priore]

Ciao maurizio ho visto che sei italiano come me, sei riuscito a trovare qualche soluzione ? esattamente come te la mia app usa una funzionalità di Push Notification, e l’unica cosa che mi hanno detta è che onesignal sfrutta la localizzazione in background…in breve dobbiamo spiegare a google che senza di onesignal tutta la baracca non funziona, ciò ovviamente è impossibile dato che cerco di contattarli da circa 1 settimana

[maurizio.polverini89]

Ciao Jason!
Ho appena ricevuto una mail dal pro-support di Thunkable, dicono che il problema sarà risolto entro questa settimana. Ci sarà un tutorial di un membro Thunkable per mostrare come risolvere il problema!

Hi Jason!
I have just received a mail from Thuankable’s support, they said the problem will be fixed within this week. There’ll be a tutorial on how to fix this issue from a Thunkable’s member!

[Jason_Priore]

Finalmente!
grazie mille finalmente il mio cliente può stare tranquillo

[wei]

Hey friends,

We are working on a fix and should be out soon.

Thanks,
Wei

[wei]

The fix is deployed. Can someone verify if the fix work?

Thanks,
Wei

[maurizio.polverini89]

I’m sending my app to revise right now, hopefully i can tell you something within two days

[Jason_Priore]

i a gree

in the requested permissions of the relise I don’t find “BACK_GROUND_LOCATION” so I think it’s solved thanks

[maurizio.polverini89]

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:

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.

[wei]

Does your app use the location sensor/Map/BLE component? If not, can you DM about project link?

Wei

[maurizio.polverini89]

No, it doesn’t at all

these are my components:

I have the same issue:
My components are:

• Alert
• Share
• Camera
• PushNotification
• Sign in
• RealtimeDB
• MediaCloud
• AdMob
• Photo_Library
• Local Storage
• Sign In

I have recently succesfully published a very similar app to the one i’m trying to publish.
It was extremely similar, 90% similar blocks too.
The difference between the one I published and the one that got rejected are:

• Alert
• Share
• Camera
• Photo Library

So i guess the problem is in one of these components. Might be a good start point to see if other rejected apps have one of these 5 components?

Hope everything will be fixed soon for eveybody!

I DM you. @wei

Thank you for your help

[wei]

Did you build and submit a new apk to the Google play store?

Wei

[maurizio.polverini89]

Yes I certanly did.
I’m 110% sure that’s the newest file and the latest I have downloaded from thunkable.

[wei]

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

[maurizio.polverini89]

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.