I faced an issue with SCORM_API_wrapper.js: after launching SCO, when pressing backspace, script runs again but the SCORM session is still "Running". In this case, Initialize("") returns "false" and GetLastError() returns "103". However, in such a case, pipwerks.SCORM.connection.initialize() returns false, preventing any further communication with the LMS. Palliatively, I fixed it by checking this case just after Initialize("") and accepting error code 103 within conditional at line 267. Maybe I am doing something wrong, but it does not seem so bacause I should not call Initialize() directly and SCORM_API_wrapper.js is unable to restore its previous state.
ps.: I faced this problem running my SCO in Moodle 2 with Chrome. I did not test this with other LMS or browsers, but it seems to me that the problem really exists.
You can't run the initialization script again, it's against SCORM policy. You can only initialize once. This is regardless of whether you use my wrapper or not.
I faced an issue with SCORM_API_wrapper.js: after launching SCO, when pressing backspace, script runs again but the SCORM session is still "Running". In this case, Initialize("") returns "false" and GetLastError() returns "103". However, in such a case, pipwerks.SCORM.connection.initialize() returns false, preventing any further communication with the LMS. Palliatively, I fixed it by checking this case just after Initialize("") and accepting error code 103 within conditional at line 267. Maybe I am doing something wrong, but it does not seem so bacause I should not call Initialize() directly and SCORM_API_wrapper.js is unable to restore its previous state.
ps.: I faced this problem running my SCO in Moodle 2 with Chrome. I did not test this with other LMS or browsers, but it seems to me that the problem really exists.