You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On all versions higher than 0.40.0 receiving
"DOMException: Failed to execute 'postMessage' on 'Window': # could not be cloned."
Also on more fresh versions also receiving:
"Failed to execute 'postMessage' on 'DOMWindow': The target origin provided does not match the recipient window's origin
Steps to reproduce
Load the widget via standard:
this.callFrame = DailyIframe.createFrame(callWrapper, {
showLeaveButton: true,
showFullscreenButton: true
})
The text was updated successfully, but these errors were encountered:
Hi! Thanks for the report. For some reason I am unable to reproduce the error you describe, but typically when we see this error it's because the code is not being run with a server (most commonly when running a local file in a browser with file://. If this is what's happening, you simply need to serve up your folder with a basic server while testing. If not, please provide more information like what browser/OS, when you see the error (on join()? or immediately?), and a copy of your console logs.
Actually, apologies, I just saw specifically the # could not be cloned. This means somewhere we're trying to send something that can not be serializable to JSON. Can you let me know what daily call is triggering this error and what parameters you are passing in?
Expected behavior
Daily prebuilt widget loaded
Describe the bug (unexpected behavior)
On all versions higher than 0.40.0 receiving
"DOMException: Failed to execute 'postMessage' on 'Window': # could not be cloned."
Also on more fresh versions also receiving:
"Failed to execute 'postMessage' on 'DOMWindow': The target origin provided does not match the recipient window's origin
Steps to reproduce
Load the widget via standard:
this.callFrame = DailyIframe.createFrame(callWrapper, {
showLeaveButton: true,
showFullscreenButton: true
})
The text was updated successfully, but these errors were encountered: