Skip to main content
S
9d ago

Corrupt riv files in 8th Wall and Unity

Runtimes: Web (JS) and Unity
Rive app: desktop (and browser too)
Hello, when editing a file in a shared workspace (free plan) our files have started to load the error screen to relaunch the app. This was happening when we tried to play any timelines or state machines to check each other's work (only 2 designers)
Then our files (shared or personal) repeatedly started to give the developers issues when they tried to integrate them. Previously it worked to copy an artboard into a new file to keep the state machine and timelines, but these files would also become useless to the developers. In the end we had to redo a file from scratch and also ended up using a V1 one riv in our final app because we couldn't use the updated one (all I changed was a colour and then it got corrupted) and our timeline doesn't allow us to redo it.
This issue happened for web handover to web (js) for 8th Wall as well as Unity.
How can we avoid files becoming corrupted or show 'had to patch file because of bad data' notification?
Are we copying artboards too many times? We rely on super rapid iteration and constant production testing. I attached the rev and riv of one of the files (this one didn't work in JS).

Thanks in advance, would love to see a solution since everyone is getting annoyed with me and I'm trying to introduce Rive into our handover workflow 🙈. Attached is one of the rev file that we couldn't use at all anymore. The error is the same as reported here: https://rive.app/community/forums/support/fsnLLkXUaA62/developer-having-trouble-implementing-rive-file---says-file-may-be-corrupt/ftRqwdjTXlue?post=1
I posted this the first time here: https://rive.app/community/forums/bugs/fsLjspgTHYcR/layout-copypaste/ftFUkEI0f22S

Coaching_V4.riv
55 KB
coaching_v4.rev
128 KB
1 reply
9d ago

That's really frustrating, sorry. :/ I just tested the .rev and it seems to be working for me us ing the Mac desktop app. Which version are you using? If it's the browser app, which browser? I'll attach a re-saved version in case that helps.

coaching_v4_1.rev
128 KB

What were the issues you had when handing it off to the developers?