...

• index_lms.html
• index_lms_html5.html  
• index_lms_flash.html - NO LONGER SUPPORTED AS OF DECEMBER 2020

It is possible that the packaged course either forces use of one of these, or uses browser detection to deliver the content in the respective type.  However, at the moment, the SCOManifest.js specifically sets 'index_lms.html' (see ExtractScormPackage() in CoreClient.cs), the consequence of this is that if the course is html5 or flash, the CurrentSCO and CurrentSCOId properties will not usually be set correctly.  This can lead to unforeseen consequences and other bugs.

To resolve this, after the course has been imported, navigate to the file collection, then the course.  Edit the SCOManifest.js, and change the 'SCOIDMapping' and 'SCOManifestMapping' to the appropriate key:

Note this does support multiple entries for backwards compatibility.  E.g.:

var myAPI = getAPIHandle();
if (!myAPI) { console.log("Mapping: Could not find API"); }
else{ console.log("APIFOUND");
myAPI.SCOIDMapping = {};
myAPI.SCOManifestMapping = {};
myAPI.SCOIDMapping["index_lms.html"] = "__6LMdt51ovdV_course_id_RES";
myAPI.SCOManifestMapping["index_lms.html"] = {"id":"__6LMdt51ovdV_course_id_RES","timelimitaction":"ContinueNoMessage"};
myAPI.SCOIDMapping["index_lms_html5.html"] = "__6LMdt51ovdV_course_id_RES";
myAPI.SCOManifestMapping["index_lms_html5.html"] = {"id":"__6LMdt51ovdV_course_id_RES","timelimitaction":"ContinueNoMessage"};
}

Testing the Package

Create a SCORM Cloud account

...