Storyline Playback on iPad/HTML5/Safari Crashes

Jun 08, 2013

I've a 30 slide course 10 quiz questions, about 17 minutes duration narrated.  Running on a SCORM LMS, it plays through to the quiz results slide and crashes cold.  The iPad will not run the course again, even after killing the SCORM resume_data and relaunching the course.

The only way to get it to run again is to clear the iPad cache completely.  Unfortunately, it just crashes again when it reaches the quiz results slide.

iPad 4, IOS 6+ (latest), runs fine in Flash on desktop computers.

Has anyone else experienced playback issues on iPad/Safari from a SCORM LMS?

Sam

4 Replies
Sam Carter

I loaded the same course on another SCORM LMS and found that the course died as above, but on this occasion, no quiz was involved.  The course was auto-advancing from content slide N to N+1, nothing special.  Again, different LMS.

The symptoms:  The iPad Safari tab(window) containing the course disappears without warning, leaving the LMS tab(window) open.

Sam Carter

A couple of other iPad/Safari playback issues, one not so critical, the other more critical.

(1) Notice the navigation bar graphic hiccup just left of the SUBMIT button.  This happens on every quiz question.

This next issue is more critical.  The above quiz question erroneously shows only 3 of 4 choices.  No vertical scroll-bar is present.  A learner would not realize that a choice (the correct choice) is missing and try to scroll.  I did, and was able to scroll and reveal the correct choice.  The following snapshot shows the above quiz question with all four choices.  (content blurred intentionally)

Sam Carter

A little more follow up about the quiz question showing only 3 of the 4 choices:

- This is happening on several questions.

- The design view of the question in Storyline shows the choices positioned higher, near the question.  No scrolling would be needed if the choices were being displayed in HTML5 the way they show in Storyline.

A snapshot of the above quiz question in Storyline:

This discussion is closed. You can start a new discussion or contact Articulate Support.