@albert I am seeing a similar issue with the location permission for a newly created app I just submitted for approval on the Google Play store. My app does not use the location component however, (and please correct me if I am wrong), the generated APK does have that permission enabled (Google reports this as ACCESS_BACKGROUND_LOCATION, ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION). Google’s new policy requires me to explain why I use those permissions but reality is that I don’t!. Even though I sent them a clear explanation why they see those permissions in the APK (because of Thunkable, that is), my app was rejected and I can’t blame Google for doing so to be honest.
So here is the question: How can I publish an app for which I have not enabled the location permissions? How can I generate an app without the above mentioned permissions since I don’t
need them and since I won’t be able to justify to Google why those are enabled in the APK?
Thanks
K