Courses not loading in updated chrome and mozilla browsers

Feb 09, 2018


Recently updated chrome browser to 64 and mozilla firefox also. After updated Storyline 360 and Storyline 3 courses are not loading, always showing loading symbol. Please check the attached screenshot. If it go like that, it will become big issue from our clients. Please resolve it.


Chandrasekhar M.

33 Replies
chandra sekhar

I think this is not problem with Flash. Because i am opening course with HTML5. In the above attached screenshot, it is showing error with app.min.js file. After Google chrome and Mozilla Firefox browsers updated, we are facing the issue. And we want course with HTML5 format only not in flash.


Chandrasekhar M.


Antje T.

We are experiencing the same issues when uploading the HTML5 SCORM package into our LMS. I am using Storyline 360 in the Articulate 360 version 1.13.14869.0, the issues occur when using Chrome v64.0.3282.167, opera v51.0.2830.40. IE and Firefox are working fine.
Any chance that there will be an update anytime soon? My deadline is expiring. Am I correct in assuming that I will need to republish the item after updating and repacking it? That would be a desaster (not just for my organisation I assume).

Alyssa Gomez

Hi Antje,

Really sorry you're hitting this problem. 

First, I did want to mention that Opera is not a supported browser for Storyline 360, so I would recommend sticking with the browsers listed here. 

Next, let's talk about the trouble you're seeing in Chrome. The original bug mentioned in this thread happens when you view content locally, but that doesn't apply to what you're seeing. 

In that case, I'd like to test your project file in SCORM Cloud to see if it works correctly in Chrome there. Would you mind sharing it with me?

You can click here and attach the file to a new thread comment. Look for the Add Attachment button. Thanks!

Antje T.

Hi Alyssa,

Thanks a lot for your support. I just uploaded the content to SCORM cloud and the content seems to work fine in Chrome. Now I need to see why the browser doesn't support the project in our LMS.

Not supporting Opera is not a big deal, it is just part of our routine to test everything in all browsers, therefore I added it to my post. I will now get to work with our LMS admins.

Antje T.

Hi everybody,

we have tested my project on various LMS platforms but simply could not get it to work on our own LMS platform. After a lot of back and forth we found a post-edit workaround for our issue that I would like to share:

After you published your file, open the folder html5>lib>scripts and open the file app.min.js with a software like Notepad. Use the finder to go to accept("text") and edit it to

accept("*/" + "*"/*AdM text*/)

Save it and upload the file as usual. Of course post-edit is definitely not first choice in matters like this, so if there is any way you can avoid this, please do so. For us, this was the only fix to make the SCORM work in Chrome v64- one of the two standard browsers in our company.

(with kudos to my colleague AdM who found the fix)

Steven Pundsack


I'm experiencing the same problem. Published courses won't load in Chrome 64 locally and on our LMS. The player is stuck in a loading state.
Currently using Storyline 3, 2:3.2.13213.0

I right clicked on the player, went to Inspect, console and displays an error about cssRules.
"Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules"

Any chance you resolved that problem?


Leslie McKerchie

Great news!  We just released Update 3 for Storyline 3. This includes quite a few important fixes and some new features as well. Check out all the details in the release notes here.  

The item you'll be interested in is:

Local playback of published story no longer working in Chrome version 64

Be sure to download and install the latest version of Storyline 3.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Lisa Whalen

We are still having the same problem here, but it seems only to bee when I add Google Analytics to the head section, which was never an issue before.  Copy/Paste the exact same code every time for every module.  The older modules still work, but my colleague is working on one now that one of our testers is trying to test on Windows 10 with the newest Chrome in 64bit, but it's  just not loading.  She's publishing for web only, so not even SCORM would be interfering. She also tried publishing for HTML5 only.  

Is anyone else still having issues?

This discussion is closed. You can start a new discussion or contact Articulate Support.