I am having similar problem (permission ) when publishing my app in Play Store.
I published AAB file & it was rejected due to having Read-Phone-State permission.
My app is about an eBook & doesn’t require any access to the phone except for saving bookmark via stored variable.
I read about past discussion in this community; 1 solution perceived as useful; via editing manifest.xml however that should work for APK format & I don’t find any discussion about editing AAB file.
Please provide solution in Thunkable platform itself as to remove unnecessary permissions before downloading/publishing the app.
Do you have Bluetooth connection in your project?
Do you have access to any other sensors such as Location Services in your project?
If you have one of the above or you have tried adding it and then removed it then you need to contact Thunkable support to remove the corresponding entries.
I believe you got the issue very wrong. There is no bug in Thunkable related to what you are describing.
As recommended earlier by @namitnagar you can add in your privacy page (this must be provided anyway) an explanation about the phone state permission just like many of us and it was accepted by both Play Store and App Store. It is clear that it is you who opt to wait with this idling as you like to call it instead of amending your privacy statement and go ahead. You have decided to wait so don’t make a lot of noise if you have to wait longer. You can, at any time, change your decision and go ahead with your app and publish it as is.
@muneer pls get yo language right.
This is not how u respond to Thunkable customer.
Even as general courtesy to free user this is not a right way to respond.
Thunkable staffs are responding to issues but not closing it. I had follow up personally via emails but when no respond made that I had to escalate in community.
I had 4 Thunkable folks responded to my query;
First it was from you that providing next path forward by asking yo colleagues to follow up & fix the issue
Later, same time Namit responded via solution that I need to fork up additional money on top what I had paid Thunkable & will pay Thunkable 10% to manage AdMob. Why should I use expensive solution?
My App doesn’t gather any data from user thus I had nothing to declare!
I’m a Thunkable user. I’m not one of Thunkable staff.
I’m a user like you and like many others in this community. I have my own apps (designed by Flutter and some by Thunkable) and with each app I published I uploaded the privacy policy as requested by the stores.
