I am using storyline 3 and after publishing the course they worked in Chrome and IE10 and FF. However after few days they are not loading on Chrome but works in IE10 and FF.
The issue is they were working fine just few days ago but all of a sudden only the loading wheel in loading, not the content.
Any idea how this has happened?
(I checked with flash version and it worked. Only HTML5 version is affected with this issue.)
I'm experiencing the same thing that just started today. It seems it might be related to the most recent Chrome update. The Storyline project has been consistently fine in Chrome up till now.
Storyline outputs were working fine with Chrome 63 version. It stopped working with Chrome 64 version. As David said, this must be something wrong with Chrome 64 version. Hope this will be fixed soon or Storyline will publish an update soon.
Thanks David for your comment. So, I am not alone with this issue :)
Please update on the thread if you find a solution.
Been working on this since Thursday when my Chrome updated. Few threads have been started which might help. Chrome has blocked local playback of files with the new update. If you open Chromes Console it seems to run an error loading cssRules in the javascript file.
Our current solution for the time being has been to roll our clients Versions of Chrome back to 63 as we work towards a solution and possibly upgrading to Storyline 360.
Articulate doesn't seem to be committing to when a fix for SL3 will roll out so other than that not sure on a permanent solution.
I did find however, when Publishing for CD and launching the "story_html5" file in Firefox it worked fine for me. Firefox 58.0.2 (64-bit) newest version.
From my experience it's only stopped it from playing locally in Chrome. I can still test it locally on IE11, Firefox 58.0.2, and Edge. It also works on Chrome when published for Web in HTML5 and uploaded to our server.
Gillian, just so I'm aware are you publishing to WEB, LMS, CD, where you can't get Chrome to work?
Thank you very much for the update and information about other threads, David. I uploaded the course to Tempshare and it worked find on Chrome. I am following the other threads for further information.
We too are having this issue - with the update - if you open the original and republish - it will fix the html5 and chrome issue - however we have thousands of objects that would need to be republished and several with originals missing as we have multiple developers - Im hoping to see a better solution for this.
When you're viewing the published Storyline 3 content in Chrome, are you viewing it locally?
If so, you probably noticed that the local playback isn't working correctly since the latest Chrome update.
The good news is, our team is working on a fix in Storyline 3 (we already rolled one out to Storyline 360). I'll let you know here as soon as that fix is ready!
Because our course is fairly complicated, it doesn't work with IE when we publish for USB. This means we can't use your player. As a result, we have been having our users (who do not have great internet access) view the modules by opening the HTML5 file with Chrome to view the course locally. So not being able to use Chrome is more than a testing issue for us. Since we are just piloting the modules right now, we have a small number of users so we have rolled their Chrome back to the previous version while we wait for this solution.
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
As far as I know, you will need to republish everything. Since it was the Browser update that caused the issue, Articulate made the update on their end which means you would need to republish in order for the update to take effect.
As I typed before, my issue actually was happening on Chrome 65...where the course was not loading at all...this is independent of the new problem in Chrome 66 that everyone is having.
So what you're saying is that if we have dozens of courses built with SL360 before that update we would need to go back and republish and deploy all of them again?
BTW I just now republished a course with the 3.15 build and uploaded it to Articulate review and the sound still not working.
I appreciate that...I realize that I am now commenting on two separate discussions about Chrome issues. As for the ticket support it read as it may be 3-4 business days due to an increased amount of tickets (likely Chrome related).
Any help from the community in the meantime would be greatly appreciated.
I am currently using the Storyline 2 and found that when we open the SCORM file by using Chrome browser, there was nothing can show. and when I use IE to open the same SCORM, all the content can show again . Can you please help ? Is that the problem of the Chrome Browser version ?
I am having same issue. All my courses that were developed in Storyline2 last week work perfectly well when launching from IE but none from Chrome. I tried from our LMS as well as from SCORM cloud.
Can you check what version of Chrome you're using? Ver. 66 of Chrome has introduced a few hiccups recently such as disabling the autoplay of content as detailed here.
84 Replies
Hi Sanduni ,
Can you please share publish file?
I'm experiencing the same thing that just started today. It seems it might be related to the most recent Chrome update. The Storyline project has been consistently fine in Chrome up till now.
Storyline outputs were working fine with Chrome 63 version. It stopped working with Chrome 64 version. As David said, this must be something wrong with Chrome 64 version. Hope this will be fixed soon or Storyline will publish an update soon.
Thanks David for your comment. So, I am not alone with this issue :)
Please update on the thread if you find a solution.
Hi Sanduni,
Been working on this since Thursday when my Chrome updated. Few threads have been started which might help. Chrome has blocked local playback of files with the new update. If you open Chromes Console it seems to run an error loading cssRules in the javascript file.
Here and here and here, are the threads
Our current solution for the time being has been to roll our clients Versions of Chrome back to 63 as we work towards a solution and possibly upgrading to Storyline 360.
Articulate doesn't seem to be committing to when a fix for SL3 will roll out so other than that not sure on a permanent solution.
I did find however, when Publishing for CD and launching the "story_html5" file in Firefox it worked fine for me. Firefox 58.0.2 (64-bit) newest version.
Any questions let me know.
This post was removed by the author
From my experience it's only stopped it from playing locally in Chrome. I can still test it locally on IE11, Firefox 58.0.2, and Edge. It also works on Chrome when published for Web in HTML5 and uploaded to our server.
Gillian, just so I'm aware are you publishing to WEB, LMS, CD, where you can't get Chrome to work?
I too am experiencing this problem. Works on other browsers except for Chrome.
Thank you very much for the update and information about other threads, David. I uploaded the course to Tempshare and it worked find on Chrome. I am following the other threads for further information.
We too are having this issue - with the update - if you open the original and republish - it will fix the html5 and chrome issue - however we have thousands of objects that would need to be republished and several with originals missing as we have multiple developers - Im hoping to see a better solution for this.
Hello everyone!
When you're viewing the published Storyline 3 content in Chrome, are you viewing it locally?
If so, you probably noticed that the local playback isn't working correctly since the latest Chrome update.
The good news is, our team is working on a fix in Storyline 3 (we already rolled one out to Storyline 360). I'll let you know here as soon as that fix is ready!
Any estimate on when the fix might be available?
Hi Lori,
I don't have an exact ETA to share at this point, but it should be soon!
In the meantime, you can drag-and-drop the output file into Tempshare. That's a quick and easy way to preview a published course.
Because our course is fairly complicated, it doesn't work with IE when we publish for USB. This means we can't use your player. As a result, we have been having our users (who do not have great internet access) view the modules by opening the HTML5 file with Chrome to view the course locally. So not being able to use Chrome is more than a testing issue for us. Since we are just piloting the modules right now, we have a small number of users so we have rolled their Chrome back to the previous version while we wait for this solution.
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.
I'm confused..when you say you release a fix for this issue what does that do for all the courses previously produced and deployed online?
I have many courses I produced a year ago on SL360 and they are not running in Chrome or Firefox now (They run on Chrome Incognito oddly).
I inspected the browser and see numerous CSS Rules errors.
If the fixes you mention deal with this, does this mean I have to go back and republish all of those older courses?
Hi Robert,
As far as I know, you will need to republish everything. Since it was the Browser update that caused the issue, Articulate made the update on their end which means you would need to republish in order for the update to take effect.
Good luck!
Can somebody from Articulate please confirm this?
As I typed before, my issue actually was happening on Chrome 65...where the course was not loading at all...this is independent of the new problem in Chrome 66 that everyone is having.
Hi Robert,
The fix you're asking about here and the current issue we are seeing with Chrome 66 are not related.
We are looking into the one you just reported and I'll make a note on the case you filed that you are seeing this in Chrome 65 as well.
Our initial testing does show that a republish in the latest update to Storyline 360, which is now update 15 does work as intended in Chrome 66.
So what you're saying is that if we have dozens of courses built with SL360 before that update we would need to go back and republish and deploy all of them again?
BTW I just now republished a course with the 3.15 build and uploaded it to Articulate review and the sound still not working.
Hi Robert,
We are currently investigating. I just wanted to share what we knew so far.
The audio is a different issue we are aware of as well. The details can be found here.
I appreciate that...I realize that I am now commenting on two separate discussions about Chrome issues. As for the ticket support it read as it may be 3-4 business days due to an increased amount of tickets (likely Chrome related).
Any help from the community in the meantime would be greatly appreciated.
No worries Robert.
We've got your ticket assigned also and you should be hearing from someone soon.
Hi,
I am currently using the Storyline 2 and found that when we open the SCORM file by using Chrome browser, there was nothing can show. and when I use IE to open the same SCORM, all the content can show again . Can you please help ? Is that the problem of the Chrome Browser version ?
I am having same issue. All my courses that were developed in Storyline2 last week work perfectly well when launching from IE but none from Chrome. I tried from our LMS as well as from SCORM cloud.
Hi Cheuk and Lauri,
Can you check what version of Chrome you're using? Ver. 66 of Chrome has introduced a few hiccups recently such as disabling the autoplay of content as detailed here.
Also, Chrome has disabled Flash by default, so if you did not include the HTML5 output that could explain the behavior you're seeing.
Let me know if you need any other help or if you'd like to share a link to your course we are happy to test it out too!
This discussion is closed. You can start a new discussion or contact Articulate Support.