iOS browser can't display HTML5 or SCORM version of scenario?

This is a duplicate of a ticket I just submitted to ELB support. Posting here to see if anyone can duplicate. URLs removed because of proprietary info.

On my iPhone XR (freshly updated), attempting to load the SCORM version results in a dialog asking permission to use accelerometer data, then a blank white screen. Loading the HTML5 version results in the dialog "Safari needs your permission to access Motion and Orientation", but the OK button does nothing and the dialog box sits on the screen forever. Note that it's referring to Safari, but I loaded the page in Google Chrome. ??

I can load the scenario in the CVR app, but that's not what my use case calls for.

Both HTML5 and SCORM versions work fine in a Windows browser.

Thank you.

Discussion (4)

Hey Carl,

I had this issue as well by launching off my website. I thought it was an iOS update issue but after a bit of messing around I figured out that iOS will not launch anything that is not on a secure website or platform. I literally added an an S at the end of HTTP and it works perfectly fine. doesnt work but does. make sure the instance is on a secure site though.

Even though you are launching on Google Chrome, Safari as the default browser asks for permission. You should still see the request for permission but it should launch. Also if you get a white screen after you have given permission, reload the page and it should display. I hope this helps you!

Our LMS most certainly uses https! Reloading reproduces the same behavior.

Update: I removed all video and the most complex 3D objects, as well as several scenes reducing the published zip to small enough for SCORM Cloud (and trying to isolate the source of the problem).

Nothing yet from ELB support.

I wanted to modify the above comment, but the site tells me, "You need the Vanilla.Comments.Edit permission to do that." I'm sure that's true. I'm also sure that this message could be rephrased to say, "You can only edit comments for one hour after posting." The latter would be more useful, in my opinion.