Forum Discussion
Storyline Suspend Data Compression
Good day!
As some of us know SCORM 1.2 only limits its suspend data for up to 4096 characters. Storyline (360) compresses its data (e.g. SL variables and such) in order to fit the limitations of t...
Well, I definitely see an inflate error getting thrown in your debug output. Hard to say what the error is though.
Perhaps modify this line:
SetErrorInfo(ERROR_INVALID_RESPONSE, "DataChunk Inflate error");
to be:
SetErrorInfo(ERROR_INVALID_RESPONSE, "DataChunk Inflate error: " + err);
That might help to give an indication of why pako.inflate is throwing an error.
Also, I might recommend opening the debug window on the first session, grab a copy of the suspend data (both compressed/uncompressed) at the end of the session, and then compare that with what is in the registration data on cloud.scorm, and with the data as then logged at the startup/resume of the second session. That will help identify if there is a strange issue with the data getting corrupted between the two sessions.
Seeing what the actual error message pako.inflate is throwing will help to further troubleshoot.
