Google has now rejected my appeal. All the weeks of effort put into making this Thunkable Cross app will be for nothing, if this can’t get resolved.
I see that @paulmw has indicated that reduced-permissions mode is further down the product roadmap for Thunkable Cross (Why is my app requesting permissions for contacts, camera, etc?)
@domhnallohanlon @jane @paulmw @wei Can you pl give an indication of by when this may be enabled?
I also see that Thunkable Classic operates differently (permissions are sought only for components that I add to my app). So I guess I could redo the entire app on Thunkable Classic, but obviously that isn’t an efficient solution. Esp since I ditched Classic in favour of X because support for Classic is set to be withdrawn in a few months.
Also, to ensures other devs dont face this issue, maybe you should mention somewhere in your documentation that Android apps targeting children should be built using Classic, and not X?