Story.html file won't load when output for LMS

Hello all,

We've been trying to supply our client with the appropriate files for a set of eLearning modules we've created for them. When we publish our Storyline 360 project for LMS (Tin Can API), our client can open the story.html file in their web browser and see the Storyline player, but otherwise only a blank white screen and a spinning load symbol that spins forever.

This is our experience as well when we tested the files. When publishing them for Web however, the story.html file seems to open and play correctly; however, the client needs them published as Tin Can API for their LMS.

Should we expect a project published for LMS to open correctly in a web browser? Should we tell the client to try running it via their LMS instead, and that the story.html file is not meant to open correctly in a web browser?

Thanks for any help and advice you can offer us!

3 Replies
Vincent Scoma

Hi There,

Happy to help! 

This article should help point you in the right direction! It discusses viewing your content in its intended environment, i.e., on a Web Server if publishing for Web Distribution. When viewing content on your local hard drive, you may encounter various security restrictions and unexpected behavior. This can also occur when sending it to others to view on their local hard drives. It is best to test the published content in the environment that it was intended for. 

In regards to publishing for LMS, it is best to upload the published content to the LMS. When the course is launched from the LMS, you'll see the right format based on the devices and browsers they’re using, and the publish formats you included.

Please let us know if you have any questions! 

Ashley Terwilliger

Hi again,

A quick update for you as well regarding the upcoming June 2020 update for Storyline 360, as we’ll add a new launch file to Tin Can API (xAPI) courses so you can view them on your local computer before you upload them to your LMS. We’ll make the same change to Storyline 3 in a future update.

See this article for more information, and let me know if you have any questions!