Storyline 3 Crashes on iPad Safari and Chrome

Hi Sagar, 

Fixes that include general improvements and prevent this type of odd behavior are not always documented in the release notes, especially in the cases of Update 10 and 11 where there were a lot of specific items we did want to highlight. 

After a series of fixes and updates our team tested a wide array of courses shared here in ELH and with our Support team and based on that we feel confident that the majority of courses are fixed. If you do have a course that is still crashing, please let us know as soon as possible! We'll want to get that course into the hands of our team for further testing and continued improvements! 

Look forward to seeing the update on Storyline 3!

Does the update correct Presenter 360 too?

Hello Ashley,

Is the fix you mentioned also for Studio/Presenter 360?  If so, when will it be pushed out as an update?

Hi Keith,

We have seen a marked improvement with the test cases that were shared with us previously, but as Ashley shared above, we are still looking at some instances to continue improving. 

I do see where you've worked and shared your file with our support team and we will be sure to update you when we can as this thread and your case is linked to the reported issue.

I am using Articulate 360 Storyline and fix appears to have worked for us. So far much better on an older iPad with older iOS with lots of tabs open, runs slower rather than crashing, so thank you.

Thanks Mark for that update - and if you're able to close out some of those tabs or other programs running in the background that'll help too! Some good things to keep in mind when you can't update your iOS or device.

We have advised users to close other tabs (not the LMS tab) to improve performance or along these lines. Thanks again.

Hello!

We are having a similar problem with one of our courses on the iPad. We have the newest updated version of Storyline 360 with all updates installed and it isn't working for us or the client.

We have published the course to HTML5 only and it's freezing randomly on both Safari and Chrome. We have tested it on SCORM cloud and it is freezing there. It doesn't freeze on the desktop, and works fine. We have had only the SCORM cloud tab open when viewing so the amount of tabs open isn't an issue either. The client is viewing it on their LMS and it also is not working and constantly freezing in Safari. We have also split the videos in half to make sure they aren't too long, and the videos still freeze in the module. 

If you have any feedback and or help for us this would be great!

Annabelle

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.

Hi Inga, 

That sounds quite different than the rest of this discussion, where the courses are strictly crashing on mobile Safari due to the way Safari keeps the memory and what Storyline is trying to load.

Are you trying to use Firefox on a mobile device, or this is on your desktop? Have you tried testing it outside your LMS? If you could share the file, I'd be happy to help, but if you can't you could look at using SCORM Cloud. It's a free testing option for LMS content.

Also, if you'd prefer to work one on one with our Support Engineers, they're always happy to help and can sign an NDA! That may also help prevent any other confusion in this discussion since the issues are different. 

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.