Articulate Studio Tin Can Packages -- Unsupported request content type text/plain

Nov 18, 2015

We're developing a LMS and using Articulate Studio '13 (upgraded to latest version) to create content for the LMS.

We're publishing the presentations in Tin Can format.

Everything works fine with the default Flash player.

When Flash is unavailable the HTML 5 player or "Mobile" player kicks in.

The HTML 5 player or "mobile player" is unable to communicate to the LRS.

In the javascript console of the browser I see the error:

Failed to load resource: the server responded with a status of 406 (Not Acceptable: Unsupported request content type text/plain) for the request ..../xAPI/state?method=GET

Why is this so?  Shouldn't the player be communicating to the LRS with the application/json HTTP Content type?  Is this a bug? According to the Tin Can 1.0 specification, requests should be made with application/json.

12 Replies
Peter Petrik

Thanks for your reply.

The LRS we are using does support the Tin Can API, the default flash version of the published packages communicate fine with the LRS. Its only when Flash is unavailable and the "html5" version of the player launches that the above error is given. Unchecking the "use Articulate mobile player" option has no effect...

So what's the difference? Why don't they communicate the same? Why does the "html5" version not  use the content type application/json ?

Ashley Terwilliger-Pollard

Hi Peter,

What browser are you viewing the content in? Also, it looks like I shared Storyline links with you vs. Studio - my apologies about that. I've updated them above. 

I think we'd want to take a look at your Presenter package to see how it's behaving and the information being communicated. Can you send it along to our Support engineers here?

Peter Petrik

We've tested this in all major browsers: Firefox, Chrome, Safari, IE etc...none of which makes a difference and the javascript console reporting is always the same...

I'll add a sample package that we are using...both here and will contact your support engineers with the package as well

Its a very simple package created with Presenter '13 upgraded to the latest version, 2 slides...


Peter Petrik

another problem with the HTML5 version is that it wants to try to post statements with an improperly formatted url:

POST https://[our_domain]/xAPI/statements/?method=PUT

instead of https://[our_domain]/xAPI/statements?method=PUT

Your support "engineers" are no help at all, trying to say there is nothing wrong, but there is something wrong.

The Flash version works fine communicating with the LRS, BUT THE HTML5 version has many issues.

Here's what I think, I think you'll have it all working with Flash, but don't know what to do with anything that doesn't support Flash


Peter Petrik

Here's a third problem with the HTML5 player:

The request parameter for the activityID is coming in to the server as "undefined"

I've replaced the authorization token with [our_token].....


Ashley Terwilliger-Pollard

Hi Peter,

I just wanted to follow up on your case as I heard from our Support engineers that they were able to reproduce the statements you were seeing in the HTML5 output and have shared a report of information with our QA team for additional evaluation. We'll be in touch as a part of your case and here in the thread once we have additional information to share, but I cannot offer a time frame in regards to when I'd hear back. 

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