Preventing WASM worker errors in console log when *not streaming*

Question

Whenever a stream has stopped, but you are still accessing the page where the IVS player has been embedded, I get errors in the console. If I try to implement a couple of iframes in another page with IVS players, these error logs are multiplied by the amount of iframes, causing the browser to crash after a while (out of memory).

Is there a way to surpress the errors? We tried to find the source, but it appears it is caused by the WASM worker ... which we cannot modify.

```
Access to fetch at 'https://[xxx].eu-west-1.playback.live-video.net/api/video/v1/eu-west-1.[xxx].channel.[xxx].m3u8?player_version=1.8.0' from origin '[xxx]' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
```

recursivecodes · Answer

Hi FB! It looks like you are using an older version of the IVS player (1.8.0). If possible, you might want to upgrade to the latest player version (1.16.0).

The message you are seeing is likely caused by trying to call `load()` or `play()` on a channel that is not broadcasting. One possible approach would be to use `fetch()` to first check that the playlist URL does not return a `404` before calling `load()` or `play()` on the channel.

Preventing WASM worker errors in console log when not streaming

Add your answer

Relevant content