We observe the following behavior with a change in Google OAuth:
- Webapps, available through Safari in iOS 9+, can run the Google OAuth stream as before.
- Webapps saved on the home screen can also execute a regular thread
- Webapps saved on the main screen with the meta-attribute
apple-mobile-web-app-capable are NOT - they are blocked by the "restricted user" error.
It seems that applications stored on the main screen that have a full-screen meta tag report their user agent as Web/1.0 CFNetwork/758.5.3 Darwin/15.6.0 , which is different from MobileSafari (it is also different from the user agent in the built-in UIWebView interface )
This is a bit of a snap, since turning on apple-mobile-web-app-capable is the only way to do a few other things, such as the autoplay sound we use to teach children math!
Anyone have any ideas along the way from this double binding? Alternatives we can think of include:
- Find a way for Google to distinguish full-screen homepage web pages from the built-in WKWebViews. (UPDATE: based on the user agents above, they can be distinguished, but Google can still block them.)
- Coax Google to allow this user agent. Unfortunately, I think that there is a rationale for blocking OAuth for full-screen webapps - without a location bar, the user cannot verify that they were sent to a legit Google login page.
- Apple Cokes will report the full-screen web application as MobileSafari, not this user agent. (?? doubtful)
- Create a native or cord version of the entire application to work around this problem.
Any thoughts?
source share