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
- SCORM 1.2 (experienced crashes on 2004 3rd Edition as well)
- iPad/IOS 10.3.1
- Does not crash on laptop and desktop browsers such as Safari, Chrome, and FireFox.
- Courses range for 40-70 screens, SCORM file sizes ranges from 17-40MB.
- Using layers for pop ups, quiz questions, narration
- Can't use the Articulate Mobile App, client requires iPad delivery
- Have developed courses of this scope in V2 with no crashing
We have tested four courses dozens of times with the above settings and have crashed on the iPad. The crashing is random and we do get a debug screen (see attached). Crashing can occur at any time but seems to occur well into the course and often when clicking the previous button revisiting screens (most set to reset to initial state). But, it has crashed before finishing the course as well and when clicking Next. There is not one screen (or type of screen) that seems to cause the crash. (Can't share courses here because they are proprietary.)
We reduced the layers and removed animations but the courses still crash. We split courses in half, but they crash.
We created a 50 screen course in V3 then recreated it in V2. The course contains one screen with text, narration, a graphic, and two pop ups. The screen is repeated 25 times. I also created 25 quiz questions.
When I test the V3 50-screen course on SCORM cloud, I crash. Usually after finishing the course and then when I am going back, but it crashes.
When I test the V2 version on SCORM cloud, I don’t crash. I can go through the course multiple course times and do not crash.
Has anyone experienced this issue in either V3 (or 360)? Our thinking is that there may be an issue with V3 and that the crashing may not occur on V2, but were wondering if anyone has crashed in V3 and rebuilt in V2 successfully or has crashed in V3 and found a workaround.
We have published dozens of courses with this scope and level of interactivity in V2 and have had no crashing. This all started with V3 just recently.
Support has been good and here is their take, "Based on the series of testing performed, this occurs on iOS devices but not on Android. The initial diagnosis has something to do with mobile devices limited resource allocation which might be the cause of the issue. However, investigation is still on-going and I'll be sure to let you know for any progress." And, "It doesn't appear to be an issue specific to LMS as it also occurs when I uploaded your content in our web server. The course will crash on random slides and will reload automatically asking whether to resume or not. I've logged the issue as a possible software bug."
Regardless, we have several courses that we need to deliver for the iPad, Safari and Chrome. We have already missed our initial deadline of this past Monday. Please let me know if anyone has come across this issue. If it is a Storyline bug, it needs to be fixed immediately.
Hi Annabelle,
Thanks for reaching out and testing it in all those spots! It looks like you also started a support case and Karla is testing your course now as well. Thanks for sharing it with her!
One question I know our team is looking for answers on specifically - what special or custom fonts, if any, are you using in your Storyline file?
I'll follow along so I can update the forum discussion here too.
By default, our LMS terminates an HTML5 course that throws a JavaScript error. We found that SL 360 published HTML5 playback regularly has uncaught errors when played in Google Chrome, IE Edge, and most browsers on MAC (Chrome or Safari).
To improve the learner experience, we modified the LMS to instead record these errors (for later analysis) rather than terminate the learner's course.
Could uncaught JavaScript errors in SL's HTML5 playback could be related to these issues?
Sam
Does anyone know when the improvements on this issue for Storyline 3 are expected?
Interested to know too.
I do not have an update to share, but we are working on it.
Recently there are multiple patches released for Storyline-360, however Articulate is taking too much time to fix (at least) critical issues of Storyline3. This also shows Articulate's priority & seriousness about Storyline3. We are stuck with Storyline3.
Sagar, agreed.
Hi Sagar and Patrick,
I'm sorry for any confusion around the recent fixes. Update 12 of Storyline 360 was released early in January and there were a few things that the update broke, and needed to be fixed immediately after it was released. Our team fixed those as fast as possible, but it didn't change our timeline for the next update of Storyline 3. It's still scheduled for early this year (2018) and we'll let folks know as soon as that's released.
One of the areas our team is digging into further with the crashing of iOS Safari is the use of any custom fonts in your Storyline course. That has been a common thread with the courses which are still crashing in Safari after the fixes put in place in earlier 360 updates. Once the next update of Storyline 3 is released, you'll have all the fixes for bugs you've seen in the most recent updates of Storyline 360.
Thanks for the update. Question, what are the safest fonts to use? Maybe
the top 3 to 5 safe fonts when working with Articulate.-Keith
Hi Keith,
Sorry for any confusion - there aren't any "good or bad" fonts for using within Storyline, but what our team was taking a look at was any projects that consistently were crashing in mobile Safari, and to see if they were using any very large font files.
If you think that matches your scenario, we'd love to take a look. Our team would want to collect a collect a copy of the TTF/OTF/WOFF file in addition to the .story file (I think you ran into it with Presenter, so the Presenter package) to examine that potential cause further. If you've already shared your project file in a Support case, feel free to respond there with your font files too.
If that doesn't match what you're seeing, not to worry - our team is still working on this one, and the font files were just one piece we were investigating.
Hi! Has this issue been fixed?
Hi Deepon,
What version of Storyline are you using? Are you also seeing courses crashing the mobile Safari browser? I'd love to know a bit more about your experience and set up, as our team is still investigating these issues.
We are having the same issue with SL3, running in Firefox. AND we have a major deliverable next Thursday. Any news on this? Same HTML 5, running off a server, not an LMS. Can't share files as they are proprietary. Really need help.
