Mike Behnke

Are you running this in an AppScript for the Google Form @psychobunny? If so, that is probably why the `getActiveSpreadsheet()` is null. It should be run in an AppScript for...

Also seem to be running into this when converting a codebase from Jasmine to Jest. Added the `/// ` didn't actually seem to resolve the issue (tests would run fine...

Make sure @ichallengediabetes that you are doing this in the SHEET associated with the Form results, not as an App Script on the Google Form. There are new APIs that...

Another report with more information: http://bit.ly/ookknE

I can try to test it later on, in our app, we use a wrapper component / widget that tests for WASM support prior to trying to instantiate Rive, and...

I was able to check and verify that I am still seeing this error. However, I'm guessing it is as you noted, that it might be using an older version...

Just wanted to update this, still seeing the same error, now using a more up to date version of rive-canvas (`"@rive-app/canvas-advanced": "^2.4.0"`). I took a look into the Emscripten code...

Closing - the [fix in Emscripten](https://github.com/emscripten-core/emscripten/pull/21511) was to remove the WebAssembly check from release builds altogether and only check for WebAssembly in debug builds. Closing this issue as it is...

Sorry it took so long to get back to this - confirmed that using `wasm-unsafe-eval` does indeed allow eliminating `unsafe-eval` if the only reason for it was for wasm support....

I don't think the script needs to be updated IF it is being used in a Google Sheets associated with the Form Results. In that case, it can continue to...