Rise Course xAPI File Structure Change??

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.

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!

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? 

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.

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.

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.xml

old statement: The statement refers to the ids given in the tincan.xml

I reached out to support and included these images and questions. All I got was the exact same message posted by DanThornton​.

Hello, 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?

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 entry 

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:

1. Ensure your LMS follows standard xAPI specifications
2. 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. 😡

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.