"Resume saved state" on mobile

Hi Adrienne!

Thanks for letting us know what's going on. I put together a quick sample file that I think matches the description you included, and this version seems to be working fine on my mobile device. Here's a link to the sample if you'd like to test it on your mobile device, as well. How did that link work on your end? Are there differences between the triggers on your file and on mine?

Thanks Alyssa. Your sample worked on my mobile device, and there doesn't seem to be a difference in the triggers. But I just tried mine again and it still isn't working :(

Hmm, that's interesting! Could you share your .story file with me (or even just a one slide sample) so I can test it out on my end? You can attach it here in the thread by using the ADD ATTACHMENT button, or you can send it directly to our Support Engineers here if you’d prefer to send it privately.

Thanks. I will send it to the Support Engineers.

Thanks for letting me know. My colleague Eloisa is testing your file now (01043867), so you should hear back shortly! 

To update for others who may be having similar problems: it turns out that objects placed on top of each other don't work perfectly in HTML5. The fix is to use disabled states instead of hiding things behind other objects. I wish I had known this before I designed the course... throwing an invisible box in front of everything is way easier than disabling every button individually!

Thanks for sharing the solution to your case, Adrienne. I'm sorry this is causing extra work on your part, and we'll definitely investigate further on why states aren't retained with the slide is revisited in HTML5. We'll keep you posted, and let us know if you have any other questions!

Hi Alyssa,

I was wondering if you had any updates on this, or if you know whether this issue also occurs in Storyline 3/Storyline 360? My organization has several courses that we'd like to offer on mobile devices, but we use this "covering things with an invisible box" trick all the time. The fix that Eloisa suggested would require adding thousands of triggers to each course.

Hi Adrienne,

It looks like Eloisa is testing it currently - so we'll follow along in your case as well! 

Just remembered about this thread and wanted to come back with an update-- this problem does not occur in Storyline 3 or Storyline 360! We've upgraded to Storyline 3 and we are very happy so far!

Great news Adrienne - Thanks for chiming back in 😁