...
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.