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
For context, the reason it happens is because we intentionally let the browser interpret an error as uncaught before we rethrow.
I understand that is thrown by the browser (source file was searchAutocomplete.jsx) and the second thrown by the react (source file was react-dom.development.js).
Added to that :
If you follow the advice in the error and add an error boundary (which you should!), you will only see the error once. So that's not a huge problem in day-to-day workflow. In fact it nudges people to add error boundaries which is nice.
In this case there is no advice mentioned by the error, How can I get the error to be thrown once ?
The text was updated successfully, but these errors were encountered:
That said I think the errors in event handlers would still be displayed twice. This is a little unfortunate but shouldn't prevent you from fixing them 🙂
@gaearon I'm trying to understand how the error will be thrown once if it is detected and in this case does it thrown only by react or by the browser. If we consider this error was shown once, does this thrown by react-dom.development.js or by the browser?
I have the same problem mention on this issue: Unhandled error is displayed twice.
The error was :
Based on the @gaearon comment and #10474
I understand that is thrown by the browser (source file was
searchAutocomplete.jsx
) and the second thrown by the react (source file wasreact-dom.development.js
).Added to that :
In this case there is no advice mentioned by the error, How can I get the error to be thrown once ?
The text was updated successfully, but these errors were encountered: