HTML 5 output crashing in Mobile Safari

Welcome to the community, Josiah!

First, you may want to make sure that private browsing is disabled in Safari. That may be causing the issue and it may be a quick fix to the problem. 

You may find that Articulate Storyline's HTML5 output doesn't load as expected in Safari when the Private Browsing feature is enabled. Please review the following article for more information:

HTML5 output doesn't load correctly in Safari with Private Browsing enabled

If you're concerned with the size of the course, it might help to try breaking the course down a little. I would recommend creating a new, blank Storyline file, then try inserting half of the slides into the new file. Try publishing this file and test it on the iPad. Does the same thing happen with the smaller version, or does it still crash? 

If you need information on importing existing slides, take a look a the following tutorial:

Importing from Another Storyline Project

If the course continues to crash on the smaller version, can you tell me if it crashes at a specific point? If so, what type of content is on that slide?

Also, I know you don't want to distribute your content in the Articulate Mobile Player, but it may also help if you could test it in the app and see if the same thing happens. This would let us know if it's possibly an issue with HTML5, or not.

Thanks and welcome again!

Hello Christine,

The course originally had 31 slides in it, and I reduced it down to 15 slides. Originally it would crash Mobile Safari within the first couple of pages, this time I was able to navigate around the course for a while before it crashed. There doesn't seem to be any specific points/pages where it is crashing. It also doesn't seem to matter whether or not I am navigating via the next/back buttons, or the menu. I had run into the loading issue earlier with the Private Browsing setting so I had turned Private Browsing off before I ever started experiencing these problems. I haven't tried running it through the app yet, but I will do that next. It seems to me as though it is just an issue with the size of the course.

Thanks,

Josiah

In my personal experience i have seen the storyline HTML5 courses less than or about the size of 10MB  package size relatively performed better than large size courses. I have also noticed there was a significant performance difference between the first and 2nd time access of course in mobile safari. When the course loaded once completely (means once all the pages and assets loaded into cache) and if the we launch it for the 2nd time the HTML5 performance was much better (I wouldn't say 100% stable but better than 1st time for sure)