Forum Discussion
Rise Course xAPI File Structure Change??
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:
Hi Dan,
Thanks for reaching out about the recent xAPI changes you've noticed. We updated the structure of Rise 360 xAPI exports to create a more consistent experience across all LMS types. Here's what that means:
What changed:
-All Rise 360 LMS export packages (AICC, SCORM, cmi5, and xAPI) now share the same folder structure.
-xAPI packages now use the most current and robust driver technology.
-The file packages themselves are organized more consistently.
Why we made this change:
This update creates a foundation for future improvements, making it easier for us to enhance LMS functionality going forward.
How to identify xAPI content:
If your export package contains a tincan.xml file, it's still xAPI content. The new folder names (such as 'scormcontent') are standard naming conventions used across all export types.
If you're experiencing issues:
Some LMS systems with custom xAPI implementations may need additional adjustment to accept our updated xAPI packages.
Check these settings:
-Ensure your LMS follows standard xAPI specifications
-Configure your LMS to use the tincan.xml file for launching content
For detailed guidance, check out this xAPI guide maintained by Rustici Software
Once your system is configured correctly, your Rise 360 content should work seamlessly-both now and with future updates.
Please don't hesitate to let us know how we can assist you during this transition.
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!
Related Content
- 6 months ago
- 10 months ago
- 10 months ago