Storyline publishing to LMS and Tin Can error

I have published using Storyline 3 and 360 with LMS->Tin Can settings of HTML5 with Flash fallback.  The HTML5 output (story_html5.html) works properly sending the info to the LRS but when I test the story_flash.html output it gives an error of  "Content type (text/plain;charset=UTF-8) is invalid for alternate request syntax".  The LRS is expecting application/json as the Content-Type.  When I debug what is being sent, story_html5.html properly sends as application/json but story_flash.html sends as text/plain.  Is this a bug in Storyline or can I be doing something wrong?

3 Replies
Crystal Horn

Hi Adam. It sounds like you’re running into a hiccup with testing your published output. I’m sorry about that!

I’m glad you shared that debugging information here. Would you be able to use these steps to test that same content using SCORM Cloud? Of course, we can help too. I’d like to try to isolate why the LRS is hanging up on the Flash version’s language.

Also, if you are publishing with HTML5 as the default output, the good news is that we support HTML5 on virtually every major browser. Hopefully, the potential impact of this issue is very small for you. Let me know what you think!

Adam DeBray

Thanks for the reply, Crystal.  I have tested using the SCORM Cloud and it works there with both HTML5 and Flash output.  It seems that it is the LRS (we are using Learning Locker), that is returning the error, but I believe it is properly returning the error because the Flash output is sending with Content-Type of text/plain instead of application/json.  Is this an issue with the Flash output?

I'm likely just going to use the HTML5 output but I would like to get the Flash output resolved in case it is needed at any point.

Crystal Horn

I understand, Adam, and agree with wanting to cover all your bases!  I'm going to open a case for our support engineers to take a closer look.

To make sure I'm fully understanding the issue, in the Flash output, the content is being labeled as plain text, but do you see if it is actually being sent as json?  I'd like to give our engineers some focus for this issue.

Thanks for bringing it up, and you should be getting an email from our support team soon.