I wonder if anyone who has experience of the Play Store could give me some advice.
I was able to get the WIMS App released for production on Monday after fulfilling the 20 testers for 14 days saga.
However, I have since run into additional issues on 2 attempts at getting the App into the Play store for public access.
On my first attempt (1.0.1), the only changes I made for the public release were to change the version number. As this was essentially the same App as 0.5RC2, I was surprised to find that it was rejected due to:
“Your app is not compliant with Google Play Policies” – “App contains icon(s) or button(s) that are not responsive or do not return content”
The screenshot they sent me indicated that it was something to do with the database navigation buttons at the bottom. The only thing I could think off was that if the user only had one record, pressing the first record (<<) or last record button (>>) might appear not to do anything.
So on my 2nd attempt (1.0.2), I added a status line that appears for 1 second indicating the result of pressing the button. I resubmitted for approval but had the same rejection notice, but this time for the Settings screen. I hadn’t changed anything on this screen from 1.0.1. or 0.5RC2
I have no idea what they think might not be working but have submitted an appeal on the basis that I don’t understand what the issue is (They just sent me a screenshot of my screen with no further explanation)
Probably an automation. Try disabling buttons that do nothing making them “unclickable”, also if they do something, that something must not delay much, it is expected some fast feedback/action/result.
The only thing I could think off was that if the user only had one record, pressing the first record (<<) or last record button (>>) might appear not to do anything.
if you are on last record you could disable the goto last record.
you could upload (copy/paste) the mentioned screenshots here too for a review.
maybe the app test/audit is interrupted if they found something and you fixed the first one by show a simple label. and now they continue at the settings page.
Everything here performs its function correctly.
The close keyboard icon in the Menu Bar is obviously only going to do something when the WFS Threshold has focus. I’ve asked them if this is the issue and am waiting for a reply.
Everything else is just standard Xojo controls.
I also get loads of warnings (minor issues) about fields not having labels and wondered if Android Studio handles these differently so that the automatic checks automatically link input fields and labels together.
They are continuously increasing the focus on “accessibility” features, that’s why the increase of warnings about fields that should have some “label” (probably said to visually impaired people) linked to them.
I did include plenty of accessibility hints with that in mind. However I made the mistake of switching on the audio hints to try it out and wondered how anyone ever has the patience to use them. It really isn’t that relevant to my app as welding inspection has minimum eyesight requirements, but they’re in there.
3rd time lucky (well technically 4th as I had to update my Play Store screenshots.
When I made the last changes, I really wasn’t sure whether the changes would enable my app to be accepted (because I still wasn’t confident about what was deemed wrong).
Anyway, in case it’s useful to others, here’s what I did:-
I checked every screen to see if any buttons or icons were active and could be pressed without (apparently) doing anything.
I added code to the affected buttons to update a status line that appears for one second. This either explained why the button didn’t appear to do anything (“Keyboard Already Hidden”) or provided additional information (“Already at First Record” etc.)
I removed any dismiss keyboard buttons that weren’t totally necessary
I’m not entirely sure that these were the non-functionality issues, but pleased to say I’m through these hurdles for now.
A couple of visual changes meant I got a “Violation of Misleading Claims policy” rejection. This was because I removed a hide keyboard menu icon but hadn’t updated the screenshot for that screen.
Thanks to all who offered me advice here - much appreciated.
