HTML5 tracking issues
Apr 28, 2015
I am using Storyline 2 and am current on the updates for the software. I am currently running into issues with courses that we would like to have accessible via mobile devices, tablets or from a personal computer.
So I have tried publishing the courses in 2 different ways (both for AICC and the user will receive completion on 100%):
1) checked the box for "Include HTML5 output" and left unchecked "Use Articulate Mobile Player for iOS or Android"
2)checked the box for "Include HTML5 output" and checked the box for "Use Articulate Mobile Player for iOS or Android"
After publishing I have the LMS link to the "index_lms.html" file.
So far we have done 2 rounds of testing and our findings is if the course is ran from:
From a computer
IE8 - user receives credit
Google Chrome - user doesn't receive credit
Mobile Device/Tablet
Safari - user doesn't receive credit
Google Chrome - user doesn't receive credit
Can anyone please offer some advice or does anyone know what the issue could be?
5 Replies
Does the Relay.ASP fix this issue?
Hey Adam -
It seems like this could be the problem. With AICC you're likely running into a cross-domain communication problem. Newer browsers deal with this differently, which could explain why it's working in IE8 and not in the other two tested.
Try this: When running the course, open the developer's console in Chrome (right-click the window outside of the Storyline player and select Inspect Element then pick the Console tab at the top of the window that opens). You should see attempted and failed communication appear as errors. If no errors appear, try looking at the network tab.
I'm guessing you'll see a bunch of errors as you go through the course, where communication is tried and fails.
Relay.asp / Relay.php might fix the issue for you as this provides an allowed channel for content to communicate to the LMS. What LMS are you using?
We are using the company RISC.
Do you need to use AICC for any reason? Or would SCORM or xAPI get the job done? I'd guess you're looking at a cross-domain problem. Not sure what platform RISC runs (IIS or 'NIX).
This discussion is closed. You can start a new discussion or contact Articulate Support.