Closed ahkhanjani closed 11 months ago
Thanks for the report! I'm not sure if something changed with Chrome's page load, but it seems like we are seeing issues more frequently on startup where the window isn't yet defined globally. We recently patched many of the places where this would trip us up but it looks like I missed this one. I've filed an internal bug and will try to squash it in the next release or two.
Fix some insecure window.postMessage() calls.
Hi @mattieruth. I assume this should be fixed now?
Seems to be fixed. Thank you
Yes! This was resolved in 0.56.0. Thank you for confirming.
Using Daily prebuilt 0.54.0, React 18.2.0, Next.js 14.0.3,
Only sometimes this error occurs:
Refreshing the page solves it. So it seems quite random. This is the client-side exception I mentioned in #229 and I'm not sure what's causing it. Since there is a problem with cleaning up effect, I assumed it has something to do with that.