HTML5 Mobile course triggers not working consistently

May 06, 2016

Hi Heroes, 

 I have provided a sample link and also attached the sample course to reproduce the problem. 

Here is my problem: 

If you click the link below on a mobile (Android or iOS) as HTML5, there are two slides that have audio. The play/pause icons are toggled and it works fine for the first time. However, after I click on the "Restart course" on the third slide, the pause icon triggers are not working as expected on the first slide (during the course revisit). The second slide triggers are working fine as expected. This happens only on a mobile device (desktop browser works fine).

Any ideas please? Thanks !

Link for replicating the problem (on a mobile device only)

http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1ai24d8401u10fl0erjbk51k0e9/story.html

6 Replies
Ashley Terwilliger-Pollard

Hi Raj,

I actually see the same while testing on Chrome desktop just the HTML5 output as well.  I'm curious if you could share a bit more information about what update of Storyline you're using (we just published Storyline2 Update 8 yesterday) and what iOS/Android operating system you're using and the browser you're accessing it in for each? Just as a note here in the information in terms of which browsers we support. 

If you could share that and then we'll be able to do a bit more testing. 

Spread Knowledge

Hi Ashley,

 Thanks for the response. When you said "I actually see the same", did you mean that you are seeing the same thing that I am seeing or did you mean that you are seeing the same behavior after clicking "Restart activity"? In short, are you able to replicate my problem or are you seeing a different behavior?

I am using Storyline 2 update 7 and I am using Chrome browser on Andriod 6.x.

Please let me know if you need any more information.

Thanks a lot !

Raj

Ashley Terwilliger-Pollard

Hi Raj,

Sorry - I meant I saw the same as you in that after clicking "restart activity" that the play/pause icon on the first slide wasn't there, although the trigger still works and I'm able to click on it to pause - you have to be fast though as it's a short word! The second slide didn't have any issues with it for me while checking in Chrome HTML5. I'll take a look at your triggers and the states associated with these items, but it may not be till early Monday (ending my day here and starting the weekend!). 

Spread Knowledge

Hi Ashley,

 Thanks for the response and the clarification. Sure, you can resume the debugging on Monday.

Another interesting thing to note here: The pause icon disappears only on the alternate slides. So, if we have 4 slides + the last "Restart Activity" slide, the pause icon disappears on the first and third slides. The second and fourth slides work fine. As a matter of fact, I had 8 slides in the original course and deleted slides 3-6 as this is just a POC. 

Thanks again, have a great weekend !

Ashley Terwilliger-Pollard

Hi Raj,

I was testing this again this morning - and the note you shared in regards to it occurring on the alternating slides was particularly interesting. I saw the same thing when duplicating your first slide and republishing to view the HTML5 output. I took a look since it seemed to be associated with your "reset the results" trigger on that last button - and a "restart course trigger" and a "jump to slide trigger" on separate buttons both worked. So I'd look at recreating that button or only using the built in "retry" functionality associated with the results slide vs. creating your own which can have unintended consequences.

Some other things I noticed when taking a look at your file -

  • The first slide had all those items grouped vs. the second slide treating them as individual items.
  • Your pause icon was set to change it's state to hidden at the start of the timeline, but you could set the initial state of an icon to "hidden" within the states panel 
  • I'd look at changing the slide properties to "resume save state" or "reset to initial state" so that way you're able to control the behavior as you wish, vs. letting Storyline control it. 

Hope that helps and also, a good reminder to ensure you're also working on local project files as detailed here which working from a network or shared drive can cause odd behavior in files. 

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