...

In the <metadata> tag there will be a <schemaversion> which should be 1.2.  If the version is incorrect, the client must re-package the course using the correct version:

Manifest Mapping

When the SCORM course is imported into the LMS, a number of files get generated including a manifest (SCOManifest.js).  This file is used to map the SCO Id, and other information desired (e.g. mastery score, time limit, etc...).

There are 3 keys that could be used by the SCORM course, depending on how the vendor created/set it up:

• index_lms.html
• index_lms_html5.html  
• index_lms_flash.html

It is possible that the package course either forces use of one of these, or uses browser detection to deliver the content in the respective type.  However, the SCOManifest.js specifically sets 'index_lms.html', the consequence of this is that if the course is html5 or flash, the CurrentSCO and CurrentSCOId properties will not be set.  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:

Image Added

Testing the Package

Create a SCORM Cloud account

...