Issues with Activities State API call in HTML5 mode Storyline version 3.2 and 360

Hi there,

We have been successfully using a custom Drupal 7 based LMS for last 4+ years in order to store activities sent from our e-learning modules using TINCAN API.

We have been having issues whereby HTML5 version of e-learning modules are no longer to interpret responses from our TINCAN API activity states endpoint. Thus always taking users to Slide 1 when e-learning modules are revisited. Problem happens in modules built using Storyline versions 3.2.x and 360. No issues when Flash version is displayed in the LMS.

Any input will be greatly appreciates. Attached HTTP request and response headers.

4 Replies
Joe Gultekin

Response HTTP RAW body is as follows in HTML5:

{"data":"26pw80i0c090f0g070d0a0j0h0e060b0k0U0~2q1~2m11001e12~2b10101201112012120131201412015120161201712018120191201a1201b1201c1201d1201e12~2N34_1001^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^v_player.5dx7NQuWAsn.6msIM0hNBuv1^1^00~25j~2i303FT4~2433400340034003400q70000121^g_default_Visitedq70000121^g_default_Visitedq70000121^g_default_Visitedq70000121^g_default_Visited3400q70000121^g_default_Visitedg600101^8_default34003400340034003400340010000~2v2031R2T3400340034003400340034003400q70000121^g_default_Visited~2r1~2n12_n~2e134003400340034003400g600101^8_default34003400w7w080191^m_default_Hover_Visited00000X03YQ0N3400340034003400340034003400g600101^8_default34000000~2C6cb101001010103jn1~2S434003400340034003400r78000141^h_default_DisabledA780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_Disabledr78000141^h_default_DisabledA780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_Disabled340034003400~2k1~2e13YX0~2413400340034003400g600101^8_default34003400q7w020181^g_default_Visited0000000~2o5cb101001010103Is1~2E334003400340034003400A780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_DisabledA780401c1^q_default_Selected_Disabledr78000141^h_default_Disabledr78000141^h_default_Disabled3400340034003400g600101^8_default340034003400~2k10~2e13yB0~2413400340034003400g600101^8_default34003400q7w020181^g_default_Visited00000000000000000002000"}

 

Ashley Terwilliger

Hi Joe,

Thanks for reaching out and sharing some specifics - I'd want to start by first confirming if you've tested this outside of your custom LMS as well. It would be good to get a baseline of how this behaves in an environment such as SCORM Cloud. Take a look at this article for steps to test out the SCORM Cloud set up with your Tin Can API Content. 

Leslie McKerchie

Hi Steve,

Thanks for reaching out and letting us know that you're running into a similar issue.

It doesn't look like we've heard back from Joe, so I do not have any additional updates to share.

  • Were you able to take a look at the troubleshooting that Ashley shared above?
  • Were you able to recreate the issue in SCORM Cloud as well?

If so, we'd be happy to take a look. With your permission, please share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.