Triggers & Variables Not Working with Users on Macs
Hello, team, I need technical support on a package.
Context
I built 4 eLearning modules for a compliance course. I built one as my template, and then copied the packages for the remaining three. I will admit to not recalling, at this point, which was the first module, but I believe it is the module I am having the problem with. The other three modules are working fine.
The Problem
In the module I am having trouble with, I have it built so that the user enters one Scene, receives one slide of introduction, and goes right to an Agenda slide (seen below) where they choose other Scenes in the module. I have received over 10 tickets, now, that users on Macs are getting through the introductory scene and the first scene of learning content, but they get stuck in a loop after the second scene. This is not happening when testing offline or online with PCs.
Here's a rundown of what is happening:
- The user starts from this page and begins the learning by going through the Scene "01 Requirements & Objectives."
- At the end of that Scene, they click "Continue."
- When they click "Continue", it adds +1 to the variable "CompletionTracking", which defaults at zero, and returns them to this page.
- When the user returns to this page with "1" in "CompletionTracking",
- the state of the lock icon to the right of "01 Requirements & Objectives" changes states from Locked to Complete
- which chains to trigger "02 Requirements in Action" to change states from Disabled to Normal.
- When the user goes through and completes "02 Requirements in Action", we repeat the cycle above.
- Click "Continue"
- Adds +1 to "CompletionTracking" variable (now equaling "2")
- Returns user to Agenda page
- When they return with variable equaling "2", instead of following the correct logic and triggers as mapped (which would repeat step #4 above but for objects and States on "02 Requirements in Action" and "03 Why Should You Care?"),
- it will show the Complete state for the lock icon on "01 Requirements & Objectives" and "03 Why Should You Care?"
- but "02 Requirements in Action" will remain in the Locked state for the lock icon.
- The state of the "03 Why Should You Care?" button will remain Disabled and the user cannot continue.
- If they attempt "02 Requirements in Action" again, it will continue impacting the states of the lock icons sequentially (meaning the rest of the Lock icons will change to the Complete state).
- The states of the remaining buttons will not change from Disabled to Normal.
The user is stuck. Only solution is completely resetting the module in the LMS.
This glitch does not occur in testing online or offline. The triggers are not built to do this.
Project File Info
- xAPI export
- Created in Storyline X64 beta
- Using one variable, CompletionTracking, to track completion as the users get to end of a scene. Clicking Continue or completing the final interaction will +1 to the variable if the variable is at the correct value for progression.
Attempted Troubleshooting
- I have no reported issues with any users on a PC.
- I've had read through and redone my triggers from scratch to control the sequencing, but it is still affecting Mac users.
- I put my "CompletionTracking" variable on my master slide and watched it as I went through the module, trying to find if a button had a trigger I forgot about or if there was any error: I could not find any issue with the trigger harness through this testing. The number always adds up correctly.
- Mac users have used Safari, Chrome, and Firefox with the same results.
- All of my other templates, using the same trigger harness, are working correctly for Mac users.
- I created a brand new file and imported the slides. Exported a new version, same results.
- Seemingly unrelated but could be an issue: I have a phantom master slide that I cannot find or delete.
I cannot post the file here because it contains company information. I do have a video of the problem happening live but I cannot publicly share that either. I could provide these to an Articulate employee for troubleshooting if that's an option.
I have also submitted a ticket.