unable to load devtool properly. Failed to execute 'postMessage' on 'Window' about apollo-client-devtools

[jerelmiller]

Hey @zhpadvoiski 👋

You're right, that PR does look like the culprit here. Thanks for bringing this to our attention!

I'm curious, are you storing URL instances directly in your cache (i.e. writing them in a merge function somewhere?) It seems URL instances don't work with structuredClone, which window.postMessage uses under the hood. Seems JSON.stringify actually does handle serializing URL instances correctly, so that would explain why its suddenly breaking for you. I'll look at getting this reverted.

In the mean time, if you need a workaround, consider using a read function to perform the conversion from string -> URL. I'll try and get a fix out for this in the next couple days.

[Sitronik]

Looks like I have a similar problem

Uncaught DOMException: Failed to execute 'postMessage' on 'Window': #<Object> could not be cloned.
    at Object.postMessage (chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:12273)
    at Object.send (chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:11729)
    at r (chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:14709)
    at chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:15415
    at i (chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:11525)
    at r (chrome-extension://jdkknkkbebbapilgoeccciglkfbmbnfm/hook.js:1:12170)

[jerelmiller]

Turns out the JSON.stringify on the cache that was previously done was a LOT more important than I realized 😅. We should be able to get this fix out today.

[jerelmiller]

This should be fixed with #1259 which we'll plan to release with 4.8.2. We should be able to get this out fairly quickly 🙂

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.