fix: catch RiveFile initialization error in hook

[damzobridge]

This PR addresses the issue with the useRiveFile hook not properly catching RiveFile initialization errors.

[bodymovin]

lgtm!

[petersli]

thank you so much! 🙌 will there be a patch release for this?

[damzobridge]

thank you so much! 🙌 will there be a patch release for this?

@petersli should be available from v4.12.1 !

[petersli]

hi @damzobridge, I think this actually doesn't catch the errors thrown by file.init() due to it being async. I think this could fix it: #270

[damzobridge]

Thanks @petersli , you're right! However, we're also working on updating the core rive-wasm package to catch all the RiveFile.init() issues and report them using the error callbacks. Once that's done we'll push out a fix for the react package.

[petersli]

hey @damzobridge, would you happen to have an eta on this? would help inform how I should plan around this issue -- for context, the update I want to make requires useRiveFile because we need to know when all assets (including rive.wasm) have loaded in. I can't use useRiveFile in it's current state because it would crash the app upon any RiveFile.init() issue.

If this fix is still a while out, I'll just roll my own version of the useRiveFile hook that fails gracefully.

[damzobridge]

Hi @petersli I would recommend rolling your version in the meantime. Will let you know as soon as the updated rive.wasm version is released.