Course won't record status to LMS - because of JS error w/ browser audio changes?

[nudoru77]

I'm troubleshooting a course that my company created and we're running into issues with a small number of users. Looking at the javascript console, I see a lot of errors and the stack trace shows the Scorm driver file in there. My assumption is these audio errors are causing the LMS connection to not initialize and thus no data is sent.

Our course has full audio narration throughout. When the course is running, turning on the Chrome (v62) Javascript/debug console shows these errors

An AudioContext in a cross origin iframe must be created or resumed from a user gesture to enable audio output.

Failed to execute 'play' on 'HTMLMediaElement': API can only be initiated by a user gesture.

On Safari, I get literally thousands of these

Unhandled Promise Rejection: NotAllowedError (DOM Exception 35): The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.

We tried publishing from Cap 9 and 10 but the error is the same on both.

Is this an emerging issue due to new media autoplay restrictions causing these errors that Captivate hasn't been updated to work with?

Thanks!

[RodWard]

Have you tried uploading the same SCORM zip package to SCORM Cloud and test to see if the same errors result from there?

[nudoru77]

I just did a preview w/ SCORM Cloud and it worked fine.

[nudoru77]

Upload the zip and previewed on Chrome (no errors here) and Safari (same tons of errors) and both completed there. I'm confused.

[RodWard]

Sounds like the issue is not necessarily Captivate's fault but could be with your LMS and perhaps due to browser security. Time to get the technical people from the LMS side involved.