We recently published a course on our LMS. It worked properly on a PC / laptop, but certain slides showed an issue when viewed on either iPhone or Android. These slides would behave normally on first visit, but when revisiting the slides the NEXT button in the mobile player would switch to disabled after about 1 second.
The course was published as restricted, restrict PREV / NEXT buttons using SCORM 2004 / 4th edition. Again, it behaved totally normally in Preview and when accessed on the LMS via PC.
We rolled back Storyline 360 to May 24th version and it worked perfectly, so we think that there was some change to the mobile player in the June 21st update.
Great call on getting a case opened with our support team. I see my colleague Eric is already handling your case! Your case is in good hands, and we'll continue troubleshooting your issue there!
Our team is having similar issues and we may have narrowed it down to slides that were out of order. We did not have this problem before we upgraded to v 3.65.28121.0.
We edited an existing course and deleted and/or reorganized pages in the previous version (that older version did not automatically renumber/reorder the slide numbers). So the previous version has 1.1, 1.3, 1.4, 1.9, 1.6, 1.8 etc. all out of order. Due to this, the Next button had to be triggered to go to the specific slide number. When we made minor text changes and republished as SCORM 2004, v3, Restricted in v3.65.28121.0, here's what was happening:
First time viewing of the slide was fine and Next button activated at end of timeline as expected (no required layers or triggers to enable or disable Next button were needed).
While testing, we clicked Previous, then clicked Next to return to the slide in question.
The Next button was enabled all the way until the very end of the timeline and then it became disabled. If you replayed the page, it usually would enable Next again. But we did not want to cause a problem for users or make them rewatch multiple times.
After trying different things, we were able to fix the problem. We:
cut and paste the slides that were out of order into the correct place which then renumbered them sequentially. 1.1, 1.2, 1.3, 1.4, 1.5 etc.
Changed all the triggers for Next to go to next slide and Prev to go to Previous slide.
This seemed to fix it. HOWEVER, we never had this problem before and I believe it only happened on iPads.
Can you verify if this is the appropriate temporary solution or is there something else we should look for or a bug that is in the works?
We're not aware of any issues like the one you encountered. I'd recommend reaching out to our support team by opening a case and sharing a copy of your project file there if you're willing so we can try to replicate the behavior to figure out what happened. We'll delete it afterwards!
5 Replies
Hi David,
Great call on getting a case opened with our support team. I see my colleague Eric is already handling your case! Your case is in good hands, and we'll continue troubleshooting your issue there!
Thank you. I wanted to post it here first in case others were experiencing the same issue and searching for others. Seems like it's just me so far!
Our team is having similar issues and we may have narrowed it down to slides that were out of order. We did not have this problem before we upgraded to v 3.65.28121.0.
We edited an existing course and deleted and/or reorganized pages in the previous version (that older version did not automatically renumber/reorder the slide numbers). So the previous version has 1.1, 1.3, 1.4, 1.9, 1.6, 1.8 etc. all out of order. Due to this, the Next button had to be triggered to go to the specific slide number. When we made minor text changes and republished as SCORM 2004, v3, Restricted in v3.65.28121.0, here's what was happening:
After trying different things, we were able to fix the problem. We:
This seemed to fix it. HOWEVER, we never had this problem before and I believe it only happened on iPads.
Can you verify if this is the appropriate temporary solution or is there something else we should look for or a bug that is in the works?
TIA, Jana Godwin
Hi Jana,
We're not aware of any issues like the one you encountered. I'd recommend reaching out to our support team by opening a case and sharing a copy of your project file there if you're willing so we can try to replicate the behavior to figure out what happened. We'll delete it afterwards!
Thanks, I just submitted the issue with 2 sample files. :D