[ARCHIVED] SCORM Issues in Chrome 80?

[steven_catania]

Does Canvas use  synchronous XHR when passing back SCORM grades to the gradebook? This is a concern based on issues with Chrome 80 and that it no longer supports the Exit Passback. More here. 

Are others having problems with SCORM grades reporting correctly to the gradebook as of early February 2020? Resolutions for those who have had problems?

[michael_rosenbe]

We are having this issue with Chrome across a variety of SCORM content. They need to update the SCORM LTI to either support the new Chrome synchronous XHR settings, or figure something out. As it is what we found still works is using Firefox and to get the grade to post at the end of the SCORM content on the results slide they must click NEXT in Canvas to get the grade to post. Jenky as heck right now.

[steven_catania]

Thanks for the response, Michael. We were using Firefox, too, but a number of our users don't have that browser and don't have admin rights to install it. We ended up having to change our SCORM grade triggers so that they show up earlier in the courses. Not ideal either, but it has worked so far.

[tuk36361]

I have been experiencing this issue since late Feb/early March and it is still affecting my SCORM grades. I have informed people to try using other browsers but some are saying Canvas is not supported on the browser they are trying. Now I am seeing some grades sent back successfully and others are not, and I am having a hard time following which browsers are working and which aren't (besides Chrome which does not seem to be working at all). I am trying enabling the flag to ignore the Chrome XHR update now and my tests have been successful, so I will suggest that to my students (who are all professors being trained to teach online), although there really should be a better solution at this point as this issue is going to affect a lot of SCORM users on Canvas. 

[steven_catania]

I agree with you, Jenny. I'm glad you've been able to find enabling the flag to ignore the XHR update to be successful. I heard back from Canvas in the middle of March that they admitted there was a bug and that engineering was working on it. I haven't heard back anything since and the behavior certainly hasn't improved when users are in Chrome.