Page 1 of 1

Cannot play SCORM content on Chrome

Posted: Fri Apr 05, 2024 4:10 pm
by wanadli
Hello ...
I'm having issues playing SCORM content created on Articulate on FormaLMS 4.x.
It's returning some JS error.
It works fine on Firefox though.

Anyone has faced this issue before?

Cheers

Re: Cannot play SCORM content on Chrome

Posted: Fri Apr 05, 2024 4:50 pm
by alfa24
Hi,
you should inspect your console developer window, first, and report errors, if any.
Alongside with front end errors, you should analyse backend errors too.

Re: Cannot play SCORM content on Chrome

Posted: Sat Apr 06, 2024 6:08 am
by wanadli
This is what it's showing.

Was wondering is SCORM working well on your Chrome?

Re: Cannot play SCORM content on Chrome

Posted: Sat Apr 06, 2024 7:49 am
by alfa24
Can you try the SCORM on other Chrome instances? Other devices, o.s., and so on? Does the issue always occur?

Re: Cannot play SCORM content on Chrome

Posted: Sat Apr 06, 2024 11:15 am
by wanadli
Yes I did. Still the same error.
Apparently happens to not just this particular SCORM package but all SCORM

Re: Cannot play SCORM content on Chrome

Posted: Sat Apr 06, 2024 11:32 am
by alfa24
Articulate storyline? Version? Could you share a test package?

Re: Cannot play SCORM content on Chrome

Posted: Sat Apr 06, 2024 11:58 am
by wanadli

Re: Cannot play SCORM content on Chrome

Posted: Sun Apr 07, 2024 4:21 pm
by alfa24
It seems it's an ADOBE CAPTIVATE package, not an ARTICULATE one.
That said, I tested it on various versions of FORMA LMS and it's working correctly on Google Chrome.
I can't test it on a 4.0.7 as it's not public. If 4.0.7 has a problem with this package on Google Chrome, I could confirm it being on your instance.

Re: Cannot play SCORM content on Chrome

Posted: Sun Apr 07, 2024 4:53 pm
by wanadli
My bad ... it's Articulate.

Thank you for testing on your side.
Really appreciate it.

Narrows down my scope of work.

Re: Cannot play SCORM content on Chrome

Posted: Fri Apr 19, 2024 2:49 am
by wanadli
UPDATE
Managed to solve this issue. Turns out it boils down to the server configuration. We had to turn off certain security protocol in server to allow the JS script through.