There are stability and accessibility issues that are preventing my app from being accepted by the Google Play store. Images and explanation below. Any help would be appreciated.
With the stability, it is saying that there is a double splash screen. I am not sure how this is happening, as there is only one showing in the AppMySite dashboard.
With the Accessibility issues, there are many.
Content Labeling, where they are recommending that icons, like keyboard drawer closers, hamburger buttons, and the icons in the bottom menu bar should all have labeling for screen readers. Is there a way to add this manually on our side? Or is this a AppMySite developer thing needed? Is there a way to get around this so I can get my app listed on Google Play store?
Touch contact size of icons being too small. I do not see any way of changing the size of these icons within the Dashboard on AppMySite, only the icon itself, color, etc. I even tried to upload my own icons to see if I could upload larger ones, but they ended up just not showing up in the actual app, even though they would show as actually uploading.
Implementation of the keyboard shows that it overlaps with other clickable items throwing an error.
Low Contrast (I was able to solve these issues with the tools available in the AppMySite Dashboard)
Any help or advise would be appreciated so that I can get my app onto the Google Play store. I was able to get it onto the Apple Store after a little back and forth with their team. But, it has been months now with Google Play.
Thank you for reaching out to the AppMySite Community.
The shared screenshots and messages appear from the auto-generated pre-launch reports on the Google Play Console.
The pre-launch reports are usually the feedback reports generated by ‘bot-testing’ and generally do not represent the app’s actual functionality.
When you upload a build to the closed/internal testing on the Play Console, the build is checked for UI/UX and basic link/button responses. The data is analyzed against the ‘ideal-app’ parameters through an automated process. If your app uses web views, it inherits the UI properties from your website, which will be different from a proper native app by design.
Hence, you may ignore the pre-launch reports as they do not impact the app’s approval or rejection decisions but serve as a guide to improve your app’s interface.
If Google’s review team has rejected your app, you will have received an email with the actual reason for the rejection. Kindly check the reason for the rejection and make changes to your app accordingly.
If needed, you can always contact our support team via chat, email, or call to resolve your issue.
Thank you for the follow up to my question, @Bennett. You are right in that they were pre-launch reports, but the results of those reports did cause the app to fail when I sent it to production… at least that is what I assumed. I did it kind of backward.
I had assumed that the AppMySite app would be good to go out of the gate, so I submitted it straight to production and it failed. I was given instructions to submit it through pre-launch to receive the reports to see what was failing. That is what I did and those were the reports that came back. I guess it is completely possible that different things occurred during the production submission than during the pre-launch, and thus different warnings were given.
Anyway, I changed what I could and uploaded a new Splash screen (a video), and submitted to both stores. Apple updated the past approved app, and Google finally (after months) approved the app and it is live on the Google Play store!!! Yay!!!
The only thing left are two warnings that do worry me. I posted another forum post here: https://community.appmysite.com/t/2-security-trust-warnings-on-google-play-store/993 to see if anyone can help shed light on these.
