[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Feedback](/c/feedback/8) # Vercel Chrome Extension Causes feedback.html Error 197 views · 5 likes · 7 posts 柚子Youzi (@youzi9601) · 2025-03-21 Hello, After installing the Vercel Google Chrome extension ([Vercel](https://chrome.google.com/webstore/detail/vercel/lahhiofdgnbcgmemekkmjnpifojdaelb)), I encountered an issue where visiting my `*.vercel.app` site for the second time results in the following error in `feedback.html`: ```log Uncaught TypeError: Cannot convert undefined or null to object at Object.entries (<anonymous>) at n (feedback.html?dpl=dpl_/* dpl token */:9:6627) ```  Steps to reproduce: 1. Visit the site using "Visit with Toolbar" mode. 2. Wait for the page to fully load. 3. Press F5 to reload the page. At this point, the error occurs. (In Chrome Devtools - Console) Once I remove the extension, the issue disappears. I believe this issue is caused by the Chrome extension. Could you please investigate and fix this? Thanks! from: [Issue #13187](https://github.com/vercel/vercel/issues/13187) Amy Egan (@amyegan) · 2025-03-21 · ♥ 1 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 柚子Youzi (@youzi9601) · 2025-03-22 · ♥ 1 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. Amy Egan (@amyegan) · 2025-03-26 There was recently another update to the extension. Does this error still happen for you on the latest version? 柚子Youzi (@youzi9601) · 2025-03-27 · ♥ 1 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:  ```javascript if ("get-tab-headers-response" === o.data.type && o.origin === window.origin) { window.removeEventListener("message", n); var s = null === (i = Object.entries(o.data.headers).find((function(e) { return R(a(e, 1)[0], t, r) }))) || void 0 === i ? void 0 : i[1]; e(s); } ``` 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! Amy Egan (@amyegan) · 2025-04-08 · ♥ 1 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 Amy Egan (@amyegan) · 2025-04-22 · ♥ 1 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](https://community.vercel.com/t/vercel-chrome-extension-causes-feedback-html-error/7423/6) was extremely helpful :smile:
