...
Languages: only English & Haitian Creole offered. MVP1 scope includes Latin American Spanish, Tagalog, and Chamorro - No bug raised - I believe this is still under development, SAF-391 & child stories. But we need clarification on where we expect to get to on langauge for tha App Store launch.
Changing language to Haitian Crole Creole after onboarding only changes the “More” screen - other screens remain in English - SAF-739.
Note that SAF-554, seen on Android, where the language picker itself often rolls back to English, was not seen on iOS.
Request for Notifications has a mis-spelling: “receive” spelled as “recieve”(twice). SAF-742.
Choosing “Maybe Later” option on Location Permissions does not work - I am still asked for Location Permissions anyway. SAF-731.
Choosing “Maybe Later” option on Notifications appears to work at first, but actually you still get asked for Notification Permissions right at the end of onboarding. SAF-731 (I documented in the same bug as it may well be the same issue - can raise a separate bug of preffered).
Having chosen “Maybe Later” option for Notifications, and then allowed them at the end of onboarding, I have managed to get into a state where the home screen has an “Allow Notifications” button, even though Notifications are already allowed in the App. SAF-738.
The “Health Departments” screen includes a “Manually Add via URL” option, which should not be present in a production build. SAF-732.
On “Terms of Use” screen, “Continue” button is closer to the bottom of the screen than all other onboarding buttons. Minor inconsistency. SAF-733.
On “Legal” screen, privacy policy still points to an outdated Google Doc. SAF-695 (this is the same issue raised against Android).
Unexpected navigation with the “About” and “Legal” screens: if you select More, then Legal, then Home, then More, you end up on the Legal screen, not the More screen. Similar to problems seen on Android. SAF-729, I added notes there.
See details below for Exposure History Page. 2 3 bugs: SAF-735, SAF-736 & SAF-736.741
Possible enhancement / improvement: In a couple of places we report “Your phone is currently outside any areas covered by Health Departments”. That’s fine, but it would be even better to refer users to where they can find information about what areas are covered by PathCheck Health Departments, and where coverage might be coming soon - ideally a reference to such a page on our website if it exists. I’ve not raised a “bug” for this, but happy to raise a “bug” or “story” to track, if one doesn’t already exist.
...
But publishing this now, so we have an initial set of test reporting to share.
iPhone XS Max, iOS 13.2
Largest screen iPhone (obviously iPads are bigger!)
No new bugs revealed by testing on this device.
SAF-733 does not manifest on this device. On the XS Max, the “Continue” button alignment on “Terms of Use” screen, matches other buttons on other screens.
iPad Pro 11, iOS 13.4.1
Largest screen of all.
App renders in portrait mode, with a large black border, regardless of device orientation:
In spite of the massive screen, the App experiences problems seen on smaller screens, similar to iPhone 6 - e.g. SAF-733, SAF-730
...
Because the link to the Privacy Policy launches a different App, it ends up in Landscape mode, not Portait mode (also Safari on this device can’t access Google docs, not sure why that is). The same happens with other browser links, e.g. links to covidsafepaths.org. (I suspect this depends on the rotation lock settings on the device - with rotation lock off, the browser will probably render in portrait mode).
...
“About Screen” shows this is rendered as a 375 x 667 screen, same as an iPhone 7 or 8 - see above.
...
Summary: some odditiesm, but as long as we are happy that it has the appearance of a Phone App running on an iPad, nothing that seems like a must-fix issue.
iPhone 7 Plus, iOS 12.2
Didn’t exspect to see anything special with this one. However, by chance I picked a device on which device-level Location services had been disabled. As a result, this is what I saw….
During onboarding, I requested to enable Location. But I didn’t get the expected pop-up - I went straight through to a home screen, asking me to enable Location Access.
It appears this device is hard-coded to not allow location access, and I don’t even have permissions to change that in the Settings (greyed out).
In device Settings, under “Privacy”, overall location services were turned off:
...
Changing that got things back to normal. So this is the same as the issue we have with device-wide location settings on Android: SAF-239, specifically point LOC-1.
Since the fix is likely to be device specific, I’ll raise an iOS bug. SAF-743.