Forum Discussion

Kyle_Erickson's avatar
Kyle_Erickson
Community Member
3 hours ago

Hi @robisorian0,

Just adding to SamHill​'s suggestions: since it works in Preview and Review 360 but breaks once published, the SCORM wrapper is the more likely culprit than the block itself. Rise changed its LMS exporter in early July and a few unlock and tracking quirks have surfaced since. Two quick checks before raising a case: were you on the new default export or the Legacy option when you published, and does the same zip behave the same way in SCORM Cloud's free tester? If Legacy fixes it, that's useful evidence to hand Articulate support.

robisorian0's avatar
robisorian0
Community Member
2 hours ago

hi Kyle_Erickson​ - thanks! I extracted SCORM using the Legacy and the default export and both showed the same error. I raised a ticket last Friday and eventually got a fix over the weekend. 

  • Kyle_Erickson's avatar
    Kyle_Erickson
    Community Member
    1 hour ago

    Good outcome, and useful to learn that both exports behaved the same. I think that points at Rise itself rather than the SCORM wrapper this time. Curious what the fix ended up being if support shared any detail, since a few of the Jul-post-exporter-change threads sound similar.