Forum Discussion
Storyline 3 Crashes on iPad Safari and Chrome
Storyline Version 3 courses crash when clicking Next or Previous on an iPad on SCORM Cloud and another LMS called Ti LMS.
Sent case to Articulate support
Published as HTML5 or HTML5/flash
SC...
Good afternoon,
Our team recently upgraded to Windows 10, which required an upgrade to Storyline360 as well (as far as I know, Storyline2 is not compatible with Windows 10). A large majory of our clients use iPads to take their training (over 10,000 users). We first published a course using 360 prior to the "fix" and then republished once we updated to the most recent version (about a week ago). However, this fix has not resolved the issue. The course freezes on the page that would lead into the results slide. We had to build a workaround (removing the results slide and setting the completion based on slides viewed- changing each question to unlimited attempts which ultimately requires them to pass with a 100%). This is not a viable solution long term. Is anyone able to give me insight as to why the course is still crashing after the fix was pushed through? Or when a permanent solution will be pushed through? We are using our brand standard font: Humnst.
Thank you for any information.
Hi Jamie. Thanks for providing those details. Would you be able to share a copy of this course file as well as your font files? We've been testing large font files to see if they're a common link in courses that are still crashing after our update.
If you can share those items, please upload them directly to our support team.
One thing to note: Storyline 2 can run on a Windows 10 desktop. Storyline 1, however, isn't officially supported for Windows 10.
Hi Crystal,
I can't provide the font files as they are licensed per user. However, I will upload the story file to the support team. Thank you for any assistance.
Hi Jamie,
Many months ago we observed that SL 360 generates any of several JavaScript errors running in HTML5 mode. (Usually an undefined variable reference) Most are non-fatal but our LMS would terminate the course on any un-caught JavaScript error. We took steps to mod our LMS not to terminate but log the error in the background.
A wide variety of errors continue to occur at random every day. Many in Google Chrome, or on iPads, iPhones, anything playing in HTML5 mode. (We know this by tracking the browser user-agent string)
If these errors could be reproduced on demand I would forward that information.
Just a reminder that SL 360 has a way to go to clean up the HTML5 JavaScript.
