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
When the react-devtools extensions is installed in Chrome is emits an event to start a connection with the react-devtools that may be embedded in an app running on the page, when you open chromes dev tools.
Ideally we would just disable the extension on all pages but the ones we need it on.
The bug may be caused by other extensions too, because the contents of message.data could be anything from any other extension, like the JS Object from react-devtools.
A simple fix is probably just a try..catch where you ignore the exceptions. Effectively whats happening now without the app crashing.
I'll throw away parsing errors as you've suggested. I believe I technically could verify the sending extension, but as soo many users like to build their own customised version - this is probably the best path forward.
Hey @iann0036 👋
When the react-devtools extensions is installed in Chrome is emits an event to start a connection with the react-devtools that may be embedded in an app running on the page, when you open chromes dev tools.
Ideally we would just disable the extension on all pages but the ones we need it on.
The bug may be caused by other extensions too, because the contents of
message.data
could be anything from any other extension, like the JS Object from react-devtools.A simple fix is probably just a try..catch where you ignore the exceptions. Effectively whats happening now without the app crashing.
former2/js/app.js
Lines 1400 to 1415 in c392397
The text was updated successfully, but these errors were encountered: