SCORM Lab · error library

The errors your package throws, explained

These are not findings from SCORM Lab's own checks (see authoring checks for those) — they are errors packages throw at themselves: a wrapper library's console message, or a raw SCORM API error code, while the course plays inside the Lab. Each page below opens with the exact error text, so if you searched it you should land straight on the right one.

• Initialize called twice in the same launchSCORM Error 101: LMS was already initialized!The course opened its SCORM session twice. "LMS was already initialized!" is the runtime's own diagnostic for a second Initialize call, not custom course text.
• A SCORM 1.2 package asking for the SCORM 2004 element cmi.learner_idSCORM Error 101: The data model element passed to getCMIValue (cmi.learner_id) is not a valid SCORM data model elementThe package is running as SCORM 1.2 but its wrapper is reading a SCORM 2004 element name. SCORM 1.2 calls the same idea cmi.core.student_id.
• session_time written in the wrong SCORM version’s formatSCORM Error 405: Incorrect Data Type [Element: cmi.core.session_time]cmi.core.session_time was written in the SCORM 2004 ISO 8601 duration format on a SCORM 1.2 package. 1.2 expects HHHH:MM:SS.SS; the write is rejected outright.
• cmi.core.score.scaled — a SCORM 2004 element on a SCORM 1.2 pathSCORM.data.set('cmi.core.score.scaled') failedcmi.core.score.scaled mixes a SCORM 1.2 path (cmi.core.score.*) with a SCORM 2004-only leaf (scaled). It doesn't exist in either edition as written.
• Storyline output throwing on a null classListUncaught TypeError: Cannot read properties of null (reading 'classList')A Storyline HTML5 player script reached for classList on an element that isn't in the page. Usually a missing or renamed player asset, or the SCO launched outside its own story.html frame.