Story not playing correctly on iPad

Hi Kevin and welcome to Heroes!

I just tested this on my iPad mini running iOS7, and everything worked as expected. I was able to click on the initial buttons, navigate to the second slide, and then click the back button to slide 1. Once there,  I could again use the next button without having to go through the interaction again. The way you had this set to publish, it was within AO on the Mobile player, so I used the same settings and you can view my published version here: http://aterwilliger.articulate-online.com/9369990171

Are you able to test this on a different iPad running the latest iOS?

Thanks for your response. However, our modules run on an LMS, and hence cannot use the mobile app. Is there any way to work around this so it loads directly in the browser?

Hi Kevin,

I had just used the settings that you had included with publish to web and include the mobile player. Since you're hosting in an LMS, can you confirm that you're using the Publish to LMS method, and you'll want to only select the HTML5 output as an option. 

Hi Ashley,

I can confirm that the settings you have mentioned are being used.

Hi Kevin,

Thanks for confirming the LMS piece. I tested it by uploading to SCORM Cloud here: http://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=5035b35b-aeb0-428b-b943-8159f6b03ffd

I experienced the same behavior you've described, and share this with our QA team. I don't have a time frame to offer on if or when they'll have a fix, so I'd recommend using another method as you work on your course. 

I would suggest not using "automatically decide" I found that it can cause odd behavior on the iPad and it is best to stick with "resume saved state" or "reset to initial state". Setting your slides to "resume saved state" may fix your issue.

I had this exact issue but needed my slides to "reset to initial state". My workaround for this was to set up a variable on each slide called "visitedSlide01" or "visitedSlide02" and set the initial value to 0. Then, I set up the next button to change to "normal" when "visitedSlide01 == Egual to 1.00" when the timeline starts. Then, I set up something to make the value change "set visitedSlide01 equal to 1.00 when state of Button 3 and Button 4 are Visited" or "set visitedSlide01 equal to 1.00 when user clicks Next" (put the trigger before jumping to another slide).  This meant that the user had to complete the slide the first time before the next button would appear, then when they revisited the slide the next button was available from the beginning. The downside is, that you must have a different variable for each slide "visitedSlide02", "visitedSlide03", etc., and takes time to program.

Hopefully this helps.

Thanks Deanna for sharing your solution here! With Kevin's slides it seemed that even resume saved state was causing difficulty in his set up, but I've shared the examples with our QA team. 

Hi Ashley, is there any news on this as of yet?

Hi Kevin,

I don't have any further updates to share from our QA team, but have shared your original files with them and the version I published so taht they could review those for testing purposes.