7 Replies
Lauren Connelly

Hi Shannon!

Let's start with understanding how it's published and uploaded to the LMS. Have you published the course for an LMS and uploaded the zip folder to your LMS? I know most Learning Management Systems use the zip folder to appropriately convert the content so that it's accessible to users.

Would you mind sharing your story file and a screenshot of what you're noticing on your end? You can either attach them to this discussion by using the "Add Attachment" button or privately send them using this link. Either way, I'll report back with my findings!

David Mangoro

Hi I have the same problem and not using an LMS, produced the content as HTML5,  it will play in FireFox, I.E11 and Edge but not in Chrome.

In Chrome it only opens the first slide but you can't click next or do anything, you just see a spinning wheel.

Any advice please as this is a very big issue for my organisation, I've been asked to reproduce the content if I can't get it to play in Chrome.

 

Sue Mullen

Same. Chrome Version 80.0.3987.149 on a PC. Storyline 360. Published as HTML5 to Articulate Review and I get the spinning wheel of death. Works fine in FF. Colleagues with Chrome are not seeing this issue. I tried republishing as HTML5 with Flash backup - same result. I have a Start trigger on page 1. The page has no fwd or back buttons by design. After clicking Start, the fwd/back buttons from (presumably) the next page appear, but the content area stays the same, with the spinning wheel. I'll send a movie to the support folks.

Vincent Scoma

Hi Sue, 

Thank you for sharing those details with us! I see that our Support Engineer Eric reached out with additional next steps. I would encourage you to continue working in your case as we get to the bottom of this! 

Please be on the lookout for his email and let us know if you have any questions! 

Lauren Connelly

Hi Meg!

I'm happy to investigate this with you! Are you viewing the course on a web server or an LMS?

The quickest way I can find the snag is by testing the file on my end. Would you mind either attaching the file to this discussion using the "Add Attachment" button or you can use this private upload link? Either way, we'll take a look and share our findings!