Thanks for letting us know. The extension has been temporarily removed from the Chrome web store while the team addresses an issue that may be related to what you're seeing.

I'll update you when I know more about the situation

Debugging Data for Issue Resolution

Hello,

Here is the debugging data I recorded when I encountered the issue again later. I hope this information will be helpful for resolving the problem. Please feel free to reach out if you need any further details.

Thank you for your support! And wishing you all the best.

There was recently another update to the extension. Does this error still happen for you on the latest version?

Hello,
I installed the fixed version of the Vercel Google Chrome extension on another computer but still encountered the same issue. Although the occurrence rate is very low, once triggered, it prevents the Toolbar from loading.

During testing, I found that this issue appears to be related to get-tab-headers-response, occurring in the following code segment:

1
if ("get-tab-headers-response" === o.data.type && o.origin === window.origin) {
2
    window.removeEventListener("message", n);
3
    var s = null === (i = Object.entries(o.data.headers).find((function(e) {
4
        return R(a(e, 1)[0], t, r)
5
    }))) || void 0 === i ? void 0 : i[1];
6
    e(s);
7
}

The error occurs when o.data.headers is undefined, causing the Toolbar to fail to load properly.

Observations from Testing

• Although this issue occurs rarely, once triggered, reloading the page will consistently reproduce it. The only way to resolve it is by clearing the cache.
• The issue appears to be related to tab-switching behavior, such as:
  • After successfully loading the Toolbar, switching to another tab and then returning to reload the page may trigger the error.
  • In some cases (e.g., after switching tabs and waiting for some time), refreshing the page makes the issue more likely to occur.

I hope this information helps with further troubleshooting. Thank you!

Thanks for doing this debugging work. That's very helpful. I just shared these details with the rest of the team and I'll update you when I learn more

Thanks for waiting. We just shipped a fix for this, so you shouldn't get this error anymore with the latest version.

Your debugging and documentation of the error was extremely helpful