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
The new xAPI file published from Rise 360 is not tracking on our LMS. I've also tested it on SCORM Cloud, which is recognising the file as "xAPI" but it is not tracking correctly on there either.
I am having the same issue today, xAPI scorm file doesn't open in our LMS. Is there some error?
Exactly what we're seeing. File structure being published from Rise is completely different. Must be some error.
I'm having the same trouble. I found there is an indexAPI.html file in the scormdriver folder that works for the basic xAPI stuff. But I used the Mighty plug-in and developed a lot (A LOT) of additional xAPI statements that now are not recognized. This severely hinders the work we were doing. It was working fine yesterday morning and now six courses are stripped of the ability to see what's happening inside the course.
I've raised a Support Ticket for this with Articulate. Don't know how to escalate further it or speak to an actual human.
Our LMS (and SCORM Cloud) is no longer able to track "Progress" of these xAPI files. And they're breaking completely on our Translator Tool.We have the same problem. Have you received a response from Articulate yet?
Hi kennethcrainer!
I'm sorry to hear that the Rise 360 xAPI update impacted compatibility with 3rd party tools!
We understand some adjustments may be required before distributing your LMS package. As I've mentioned to others, we've outlined a process to follow to get your SCORM packages back up and running quickly.
Please let us know if you need anything else!
Hi Kenneth,
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.Hi Benji,
Thank you for sharing this converter as a potential solution for the update’s impact.
I’ve tried using it to address the xAPI structure issue, but after replacing the affected module with the converted version, the course enters an endless “Your content is loading” screen. Do you have any insights or suggestions on what might be causing this or how to resolve it?
I appreciate any guidance you can offer.
I received instructions from the support how to make it work. I wander was there any communication previously about the change?
To make sure your export works correctly in your LMS, please see the following PDF for instructions on how to integrate xAPI content into an LMS.
Incorporating a TinCan LRS into an LMSHi SandraAria-501b!
Thanks for reaching out!
It looks like you were working with my colleague Angelo in your support case. I see that he replied to your e-mail on 12/05/25, sharing additional insight on your request.
Also, the Rise 360: Version History is a great resource to keep handy. There, you can stay up to date on new features and enhancements. Such as the improvements we've made to Rise 360 xAPI file structure.
Please let us know if you need anything else!
Also, not sure if it's helpful but I get basic xAPI statements from Rise when I point the LRS to the indexAPI.html path found in the /scormdriver/ folder.
Still haven't received any reply from my Support Ticket submission, but our software reseller chased up and received this from a Customer Support Specilaist:
"We've recently updated the structure of Rise xAPI exports to create a more consistent experience across all LMS types.
Here's what that means:
What changed- All Rise exports (AICC, SCORM, cmi5, and xAPI) now share the same folder structure
- xAPI packages now use our newer, more robust driver technology
- The internal files are organized more consistently
Why we made this change
This update creates a foundation for future improvements and makes it easier for us to enhance LMS functionality going forward. It's not just cleanup—it's preparation for even better features.
Identifying xAPI content
It's simple: if your export package contains a tincan.xml file, it's still xAPI content. The folder names (like "scormcontent") are just standard naming conventions we use across all export types.
If you're experiencing issues
Some LMS systems with custom xAPI implementations may need adjustment. The solution is straightforward:- Ensure your LMS follows standard xAPI specifications
- Configure your LMS to use the tincan.xml file for launching content
For detailed guidance, check out the xAPI guide.
Once your system is configured correctly, your Rise content will work seamlessly—both now and with future updates."
How such a substantial change can be updated and released without letting users know is absolutely mind-blowing. 😡Hi DanThornton!
Glad to see the community has been assisting you!
I see that your support case is being handled by my teammate, Lea. It looks like she replied to your e-mail on 12/05/25. It's possible the e-mail slipped by or was accidentally diverted to a SPAM folder. No worries! I've just resent that e-mail to you again. In case it still doesn't come through, I'm happy to share the contents of her message here, for your reference:
Also, I'd like to highlight our Rise 360: Version History. This is the best place for users to stay up-to-date on recent features and enhancements we've released. Such as Rise 360's xAPI file structure.
If you have any follow-up questions, feel free to reconnect with Lea through your case!
I'm happy to be proven wrong, but I can't find any reference to the new export in the history version. Where can I find the reference you mentioned in the changelog?
This is the last entryHello, we too cannot upload a working xAPI file to our LMS due to the restructure of the files. Can someone please respond with a solution?
We managed to get the xAPI files running in our system. KateEllis-78638 make sure you adjust the launch path. It changed from index.html to scormdriver/indexAPI.html. You should not restructure the files. Upload them as they are.
UPDATE
Support reached out to me and told me that they will revert to the id usage for xAPI in the next update! 🥳
Old Message
Hey guys,
We are wondering why the statements do not use the proper ids anymore. All the ids are still defined in the tincan.xml. Instead of using them, the statements use parsed names of the activities and replaces blanks with underscores. Additionally, there is other regex magic included. Why is the usage of the ids replaced by that unprecise strategy?
new statement: Why are they parsing the names instead of using the ids? The ids are still there in the tincan.xmlold statement: The statement refers to the ids given in the tincan.xmlI reached out to support and included these images and questions. All I got was the exact same message posted by DanThornton.
Hi ittaq,
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.Hi,
Did they give you a date for this update? This is also a breaking change for us.
Hi AnnDunbabin!
Sorry to hear that the Rise 360 xAPI file structure enhancement caused trouble for you!
I'm happy to share that we released an update to this functionality on 12/12/2025. You will have to republish and reupload the content to your LMS. However, this update should resolve most issues users were facing during LMS playback.
Please let us know if you run into any setbacks moving forward!
Hello everyone!
This update from Articulate broke our critical business functions. As such, we needed a work around. I have hacked something together for our purposes, hope it helps ya'll as well. It's free and only provided as is with no support. I just fixed it for us and hoped others could benefit.
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.
