Android Pre-Launch Report: should I be concerned?

The place to discuss anything and everything about running your LiveCode on Android

Moderators: Klaus, FourthWorld, heatherlaine, kevinmiller, robinmiller

Post Reply
trevix
Posts: 588
Joined: Sat Feb 24, 2007 11:25 pm
Location: Italy
Contact:

Android Pre-Launch Report: should I be concerned?

Post by trevix » Sat Nov 28, 2020 11:58 am

After uploading my App to the Google Play Console, I have a bunch of warnings on several devices.

1 - Accessibility: content labeling: unreadable by screen reader
2 - height of input field less then 48 Pt (! wow)

I tried to enable TalkBack on the device (Google suggestion to see if th screen reader can read my labels) but it doesn't work: the all window get selected, no matter the size of the label.

Beside that, I've got a Crash on Motorola Moto e5 Android 8.1. Crash data are meaningless to me so I guess my only choice is to exclude the device?

The point is: how should I interpret the Google Pre-Launch report for a LC App? Disregard them all (LC is a different beast)? Follow the suggestions for bigger input fields and also bigger labels? Force the test black on white background?
Is there some LC lesson that talks about this?

Thanks
PS The App works fine on the few hardware devices i own.
Trevix
OSX 10.14.6 LC 9.6.0 Dp2 iOs 9.3>

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5837
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: Android Pre-Launch Report: should I be concerned?

Post by jacque » Sat Nov 28, 2020 10:37 pm

If the notice says something about warnings that you may want to address in future updates, then you can ignore them. I wonder what your app does though, since I've never seen either of those.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

trevix
Posts: 588
Joined: Sat Feb 24, 2007 11:25 pm
Location: Italy
Contact:

Re: Android Pre-Launch Report: should I be concerned?

Post by trevix » Sun Nov 29, 2020 10:25 am

On first opening, my App display the following screen:
- language choice
- registration
- login
- change of password

First, let me say that all the reports concern "Accessibility". I guess that this regards visual unpaired users and, being my App a Sport App, probably i can disregard them. Is this correct?

Second, the (automatic) Pre-Launch robot, never went past my "registration" (I don't know if it is possibile to instruct the robot how to handle this in a LC App).

The robot just click here and there, ending to the password change screen (where it report the input fields being less then 45 Pt.
See the following screen shots:
Schermata 2020-11-29 alle 10.07.54.png
Schermata 2020-11-29 alle 10.06.37.png
Schermata 2020-11-29 alle 10.03.51.png
Trevix
OSX 10.14.6 LC 9.6.0 Dp2 iOs 9.3>

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5837
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: Android Pre-Launch Report: should I be concerned?

Post by jacque » Sun Nov 29, 2020 11:16 pm

I suspect the warnings were caused by trying to implement TalkBack which is specifically designed for sight-impaired users. Disable or undo that and I think the warnings will go away. If it involved editing the manifest, revert to using the default LC manifest. If you selected any of the Requirements and Restrictions in standalone settings, paricularly fake touch, uncheck them.

The warnings are just recommendations and you can ignore them, but unless you can remove TalkBack they will appear again on every update. There is no way to instruct the auto-review to look at any particular thing in the app.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

trevix
Posts: 588
Joined: Sat Feb 24, 2007 11:25 pm
Location: Italy
Contact:

Re: Android Pre-Launch Report: should I be concerned?

Post by trevix » Mon Nov 30, 2020 6:02 pm

Talkback is not enabled on my App (I didn't even know that it was possible to enable it in LC).
I think that this is part of the Google robot exploration. To determine if the App is correctly done, TalkBack is used to find out if a label or field is correct.
If it can't read it, it display the alerts.

My question is: does the auto-review recognise the LC fields and labels?
Trevix
OSX 10.14.6 LC 9.6.0 Dp2 iOs 9.3>

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5837
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: Android Pre-Launch Report: should I be concerned?

Post by jacque » Mon Nov 30, 2020 6:51 pm

Okay, I thought you said you were trying to enable Talkback. I've submitted several Android apps and never seen those warnings, so LC fields aren't a problem. It sounds like something in your app makes the review process think the app uses Accessibility features.

Did you select any of the Requirements and Restrictions in standalone settings? Have you modified the manifest? If not, I'd just ignore the warnings.

I usually make my buttons and field text somewhat larger, so maybe I'd get the same warnings if I didn't. There are recommended sizes in the Android HIG to accommodate mobile displays with high resolution and I try to follow those.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

Post Reply

Return to “Android Deployment”