Our RawNFC app has been submitted to Google for review and has been rejected twice now because of reviewer stupidity. First it was because they claimed we were making false claims due to our screenshot showing Mifare Classic on a list of tag technologies when their test device did not support it (hence it was not shown).
After appeal, they are now rejecting it because the app “contains very little content and does not provide an engaging user experience”.
I’m glad I’m not the only one… Being a non-professional dev has made every step with Google an nightmare.
To this day I can’t claim ownership of the Google result (knowledge panel) of my OWN games because I don’t have an official documentfrom the company that made them… Even though there’s no company involved and I use the same account that published them
My clothing company shares an official address and selling space with another store but I can’t verify and set the address on Google maps because I can’t send them a video of a sign with the actual name on it. I’m actually loosing customers daily because they’re not satisfied with actual official paperwork.
And I’m not even mentioning all the censorship and content issues I’ve had with publishing apps like you do. Those using the adult edition checklist know how hard it was to update it
Anyway, all I can tell you to help is that the apps are not reviewed by a human. Very often an insignificant vhange and reupload will change the result drastically. In your case adding a credits or settings page would most likely fix the issue.
For example on my adult app I would sometimes just re-upload an almost identical app and it would work on the second or third try.
It’s a bot clicking and writing randomly, it’s not a human. The point is to open as many menus and pages as possible to check for porn and other triggers. Even the screenshots are not checked by a human.
You can trick it pretty easily to hide things or pretend there’s more content.
I think adding a modal that says “Place Transponder near phone” when executing the command may satisfy the functionality issue since the bot obviously doesnt have thumbs to grasp a transponder
This is weird. I’ve never had an issue like this when publishing to the play store. All of the apps I’ve published thus far are basically useless without the right NFC tag, so I know they haven’t even really been able to test them, and I get immediate approvals every time.
It has to do with the fact that there’s a single activity with very little UI in it. The apps are not tested by humans, let alone with NFC hardware or any hardware at all. It’s just an AI checking for basic criteria.