Safari crashes on iPad 2

Hello,

i am having an issue with a Storyline project.  It works fine on an iPad 3, however it crashes every time on an iPad 2.

The project has roughly 40 slides with 2 scenes, each slide has audio and multiple triggers, and the first slide has a JavaScript trigger that shows a timer for the audio duration per slide.

When I call the project, it shows the launch screen, and then dies.  I am not using an LMS, however it is on a server.

I'm sure that sounds pretty vague, but I'm wondering if anyone has run into anything like this and to give me some instruction.

Thanks so much.

9 Replies
Christine Hendrickson

Hi Kurt,

Unfortunately, Articulate cannot provide support for JavaScript, so if it's an issue with this, we won't be much help. However, if you're able to test this without the JavaScript and encounter the same issue, we'd be happy to try to help resolve the issue. 

First, can you confirm that Private Browsing is disabled in Safari? To find out how to do this, please see the following article:

Articulate Support > HTML5 output doesn't load correctly in Safari with Private browsing enabled

If the problem continues after disabling Private Browsing, we'd be happy to take a look at the files and see if we can pinpoint the issue.

You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Sam Carter

Kurt Masteller said:

Hello,

i am having an issue with a Storyline project.  It works fine on an iPad 3, however it crashes every time on an iPad 2.

The project has roughly 40 slides with 2 scenes, each slide has audio and multiple triggers, and the first slide has a JavaScript trigger that shows a timer for the audio duration per slide.

When I call the project, it shows the launch screen, and then dies.  I am not using an LMS, however it is on a server.

I'm sure that sounds pretty vague, but I'm wondering if anyone has run into anything like this and to give me some instruction.

Thanks so much.


It will be some work, but can you run a test without your JavaScript to see if the behavior changes?

I assume both iPads are running the same IOS.

Karen Allen

We have the same problem. Private browsing has been disabled. Our decks are sooooooo plain and simple. we removed builds, absolutely nothing fancy, audio is as specified in the storyline specs and still crashes. Huge problem for our business. Folks at artiuclate have not been able to help at all

Very disappointing to say the least. We are looking for a new solution for a hug project to produce eLearn that place on PC and iPad.

Sam Carter

Karen Allen said:

We have the same problem. Private browsing has been disabled. Our decks are sooooooo plain and simple. we removed builds, absolutely nothing fancy, audio is as specified in the storyline specs and still crashes. Huge problem for our business. Folks at artiuclate have not been able to help at all

Very disappointing to say the least. We are looking for a new solution for a hug project to produce eLearn that place on PC and iPad.


http://community.articulate.com/forums/t/25288.aspx

Christine Hendrickson

Good morning Karen,

I apologize for the frustration. I took a look this morning and I've only been able to find one case opened under your name with our support team. This case dates back quite a ways, so I'm not entirely sure if I'm seeing the communication you're referring to.

"Folks at artiuclate have not been able to help at all"

Do you have any case numbers for this specific issue? I just want to make sure that I'm not missing anything here. I certainly don't want you to feel like we haven't tried our best to assist you. Our customers are extremely important to us, so if we missed anything I apologize. Please let me know if I can pull some case information and get you in touch with one of our senior technicians for assistance. 

Thanks very much Karen,

Christine

Marco Bennardo

Hi Christine,

I have a similar issue with a Storyline Project with 60 Slides and 41 min.  of audio. I have no trigger based on  Javascript. Safari on iPad 3 crash after the course start. I have split  the course in two parts of 20 min. and now the course do not crash. I there any limitation on number of slides or project duration?

Thanks very much

Marco

Christine Hendrickson

Hi Marco,

There aren't really any limitations as far as creating the projects, but viewing them depends on the device, the content, how it's being viewed, etc. If the mobile device or output type, or even the internet connection cannot handle the size of the course, it can result in the course crashing. 

What size is the course that you're publishing for the iPad? Sounds like splitting the course did the trick for you, so I'm guessing that the original size was quite large. Is that correct?

Thanks!

Anantkumar Malikaveetil

Hi All,

We faced the same problem on a huge Flash to HTML5 conversion project for iPad. Without getting further into the internal and client frustrations that we had to face, let me get directly to our understanding : )

Storyline output on iPad Safari might not function as expected due to multiple reasons correctly pointed out by Articulate team. It's not just Safari but the courses would also crash on other browsers. It's primarily to do with the browser resource allocation and memory management on iPads. It is said that the newer version iOS7 has better resource allocation and memory management for browsers and apps, but it still remains to be seen and validated. We found the crashing issues even on the latest version of iOS7.

Till we have a Storyline fix or a better version of iOS/iPad here's something that could help. We found that having light weight pages and lesser number of slides per project helped. We had the audio and image compression settings to the optimum and were able to have courses up to 45-50 slides run without a crash. The results were more consistent with pages in the range of 25-30. The saving grace was the SCORM bookmarking which allowed the learners to restart a few pages ahead  from where the crash had occurred.

I don't see fixing the Safari's crashing issue as Apple's immediate priority, so I guess it's up to the Articulate team to find a fix. I see a lot of learning companies struggling with similar issues and in danger of losing business and clients.

I sincerely hope Articulate team finds a fix very soon! : )