Forum Discussion
Rise Course xAPI File Structure Change??
I'm creating courses in Rise 360 and publishing in xAPI (TinCan). The published xAPI file structure from 3 days ago is completely different to the file structure when republishing the same course today.
In fact the new xAPI file structure contains "SCORM" files??? See images.
40 Replies
Hi Dan,
You can find everything you need to convert your post-December 2025 release into a format that older/custom LMSes will both accept and track xAPI statements. This also works in SCORM Cloud.
https://github.com/ijnebzor/rise360-xapi-legacy-converter
Feel free to download, fork and use as you see fit.
⚠️ Disclaimer- This is not an official tool.
- It is not supported or endorsed by Articulate.
- It is provided as-is, without guarantee.
- Use at your own discretion and responsibility.
- It was created to solve our organisation's needs and is shared publicly in case it helps others.
If this solves your problem, amazing. If not, feel free to fork, modify, and improve.Ok, so the third party solution for converting post-December xApi packages is the only way to be able to update old packages in the LMS? Otherwise you will have to replace the package and then the users will loose all their progress. Has there been a heads-up for this change?
We found an additional issue beyond the activity ID problem.
The new xAPI exports use Rustici's SCORM driver (scormdriver/indexAPI.html) instead of Articulate's native xAPI implementation (index.html). Even though the driver is configured for TCAPI (xAPI) mode via driverOptions.js, the communication layer (AICCComm.html) looks for AICC-style URL parameters:
- AICC_URL (instead of endpoint)
- AICC_SID (instead of the auth token)If your LMS passes standard xAPI launch parameters like ?endpoint=...&actor=..., the driver won't find them and silently fails to send any statements to your LRS.
Workaround: We added both parameter styles to our launch URL:
?endpoint={lrs}&actor={actor}&token={token}&AICC_URL={lrs}&AICC_SID={token}This lets both the old native xAPI structure and the new SCORM driver find the endpoint they're looking for. We're testing this now.
Hope this helps others who are stuck!
Has anyone tried publishing xAPI again and uploading it to LMS, is it working now for you? I still get error message when displaying the course in LMS.
Based on this update and information it should work.Hi SandraAria-501b I'm having issues too, it's not just you. I can't upload anything to our LMS. last successful upload was in November- tried this week and getting nothing. It's causing huge issues.
Hi NicholaHowarth!
So sorry to hear that your Rise 360 xAPI output is not uploading to your LMS!
I see that you're currently working with my teammate Jan, through a support case. It looks like he just replied to your e-mail, sharing insight and troubleshooting steps.
We can continue the conversation through your case to keep all information in one spot!
Hi SandraAria-501b!
Sorry to hear that Rise 360 xAPI packages are still slowing you down!
I noticed that you were previously working with my colleague Angelo, through a support case. I've updated your case with the recent feedback you've shared, so Angelo can be kept in the loop.
He should be reconnecting with you via e-mail shortly!
We are still having a lot of issues as well.
My support ticket was closed through Articulate, so I seem to be on my own.Hello SaraMartin-7635,
No need to be on your own! I checked our system and can't seem to find your case. Do you happen to have the case number for the closed case? I'd be happy to look into this for you.
If you can't locate the support case information, please feel free to reach out in a new support case so we can continue the xAPI file structure conversation.
Thanks for letting us know!
