iOS7 and Storyline

Sep 18, 2013

Now that iOS 7 is out, I wonder if anyone has had a change yet to test a Storyline project in both HTML5 and Mobile Player App and if there may be any Storyline-iOS 7 issues.

107 Replies
XAn Choly

Hi Scormcloud, ios7 & update4 users,

Try this:

Publish a course in Scorm 1.2 & include HTML5 output and Use Articulate Mobile.

Upload it to ScormCloud and test the course using the invitation link.

The course plays fine when viewed on a desktop browser.

When viewed on an ipad the Mobile App attempts to launch the course but constantly fails.

I have tried everything but can't get it to play on the ipad.

I've also had issues where the course just keeps restarting over & over in mobile safari when output as html5.

Try this:

Publish the course to TinCan - try to upload it to ScormCloud. You will see another issue where Scorm Cloud refuses the Storyline TinCan version.
 

Both cases are being investigated by Support # 00370471.

Just thought I'd share it here as well.

Ashley Terwilliger-Pollard

Hi Xan,

I saw that Jayem sent you another message today, and shared the following: 

We have verified that SCORM published content will not work launch on Articulate Mobile Player because of the authentication mechanism of SCORM Cloud. More information about this is outlined here: 
http://www.articulate.com/support/storyline/cannot-access-content-error-when-launching-articulate-storyline-content-in-the-articulate-mobile-player 
(Please see under "Your LMS or web server requires learners to login to view content topic") 

Rob Skeet

I have read through all of this thread and have tried Micah's .js file.

nothing seems to make a difference here.

I have a bunch of storylines embedded into moodle pages.

they work on every platform and every browser except the iPad

(I've tried both Chrome and Safari.)  Puffin works with Flash but It is not practical to have potentially thousands of users downloading puffin to work on their ipads.

2 main problems.

First is the PLAY button that the Story_html5 shows before the page loads.  This looks unsightly and is a royal pain for users.

Second, once the page loads, it appears that the story is too big for the iFrame and gets cut off on the right and has a big white space on the left.  I have adjusted both the size of the iframe and the size of the Story but nothing changes.

This product has already been released and now we are having folks calling up and complaining.

Any one?

Justin Grenier

Good Afternoon, Rob.

I'm happy to respond to both of the issues you raised:

1.  In order for Mobile Safari on iOS 5 to auto-play media like audio or video on the first slide, there must be a user interaction.  Thus, we display a Play Page to handle the interaction.  The limitation is only in Safari on iOS, not other Desktop browsers.  If you'd like to see a change to this behavior, we welcome your Feature Requests!

2.  Although you won't find our content being cut off at SCORM Cloud (an industry-standard tool for testing SCORM content), Moodle cutting off the bottom of the player has come up several times within the Community:

I'd recommend reading up on the above threads and maybe checking directly with some of these folks to see how they fixed this Moodle issue.  The author of the SCORM module in Moodle is also a frequent contributor here in our Forums, so you might consider sending Dan a Private Message as well.

Good luck with your project!

Rob Skeet

Thanks Justin and Phil!

I have tried all the .js modifications mentioned in the articles above and am using the latest version of Moodle.

Still no luck as yet.

I am simply embedding these interactions in a Moodle web page using i-frame and not actually using them as SCORM courses,

it appears to be the layout of the story_HTML5.html file that is causing the problem but I have no idea what .css file to edit

in order to alter this.  since all other devices are defaulting to the flash player that works seamlessly, I can't use developer tools to zero in on the .css.  Any ideas?  Phil, which .css were you referring to? 

is there a way to bypass the story_HTML5.html file and just go to the actual content?  does this exist?

Sorry, as many others have mentioned, I used storyline for this project because of the HTML5 output  for iPad but it appears that it's not quite there yet.

Any other thoughts?

Rob Skeet

Phil Mayor said:

Hi Rob the issue with cutting off is Moodle you can either edit your CSS or install the latest version of Moodle in which I believe this has been fixed.


Hey Phil,  do you have any thoughts on what .CSS needs to be altered for this issue?  I am using the latest Moodle version and an altered "essential" theme and am having no HTML5 love.  any thoughts would be greatly appreciated!

Rob

Sue Rennoldson

Hi Ashley,

This issue is not confined to Moodle, as HTML5 content displaysin exactly the same way as described via our LMS in iOS7 for iPad. Controls atthe bottom of the player are partially visible if there is a sidebar, but notat all if there is no sidebar. This was not a problem in previous versions ofiOS. Are you working on a fix? If LMS configuration can make a difference, whatdo we need to do? I’d appreciate an update as tinkering with a huge number ofjs files is not feasible for us and neither is the mobile player.

Thanks!

Sue

Ashley Terwilliger-Pollard

Hi Sue,

Welcome to the Heroes community! 

We're aware that the issue isn't confined to Moodle, but it is happening in LMSs that display it within an iFrame. Moodle is one example,and one  of the contributors here in our forums is also contributing to the development of the SCORM for Moodle and he shared that it's something the Moodle team is looking into as well. Since each LMS has a different player set up, it's great if you can also connect with your LMS team to see if they have a fix to display the content outside of the iFrame while our team continues to look into a broader fix for all Storyline published content. 

If you'd like to share some further examples with us and what LMS you're using, I'm happy to add them to the open issue for our QA team to see. It would be great if you could provide a link to a published course on your LMS and some images of the behavior on your iPad. If you'd prefer not to share here in the forums I can send you directions on how to share with me privately. 

Douglas Brown

I do see everyone happy with running on their Ipads, but can you tell me are you running them on an LMS - we use Moodle - just trying to get Storyline and Moodle to work together on an Apple and Android pad in Moodle.

Don't currently see them as compatible - we are just up to Moodle Version 2.5, eventually going to 2.7 around May of this year.

Any ideas?

Cédric Mallet

Hi

did anyone came to a solution regarding Storyline courses uploaded on a moodle site and viewed on iPad ?

My setup is :

- Storyline update 5

- moodle 2.7

- trying to have users access the course through the moodle SCORM player. I would love to let users get the content for the Mobile App Player, but moodle would not deliver the content to the App.

I use the "Resize browser to fit screen" option on AS player, and open in a new windows on moodle.

It works fine on computers and iPad when in portrait position, but the player is cut when rotating to landscape. This is really a blocking issue for us because users will be reading the content in the landscape position. With the player menu adding a column on the side, the portrait position is just not usable.

I have tested outside of moodle and have to say it works fine. The issue comes from Storyline being used with moodle SCORM player. I am unable to say if the bug is on Articulate or moodle, yet I can definitely see some javascript code resizing the window to the wrong dimensions when the course is loading in landscape position.

I have seen many contributions by Dan regarding use of AS on moodle, is this a known issue ?

Thanks

Dan Marsden

Hi, 

Hopefully we'll eventually get native support for Tin Can in Moodle and be able to support the Mobile App player but it might be a while before we manage to get that all sorted - especially as no-one is currently providing funding to complete the work.

No one has reported any issues with mobile devices, SCORM  and Moodle 2.7 in the Moodle Tracker but If you could provide very specific information on how to reproduce the error it would be great if you could create a new issue.

In the Moodle Tracker issues we need:

Screenshots of the problems and full information on how to reproduce including all settings used in the SCORM (current window vs new window etc)

Information on the core Moodle theme that allows us to reproduce the issue - if your issue is with a 3rd party theme you will need to report it to the theme developer - not to me.  

A SCORM Package that allows us to reproduce the issue.

thanks,

This discussion is closed. You can start a new discussion or contact Articulate Support.