Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: "Minified React error #16921

Closed
jpelaa opened this issue Sep 27, 2019 · 4 comments
Closed

Error: "Minified React error #16921

jpelaa opened this issue Sep 27, 2019 · 4 comments

Comments

@jpelaa
Copy link

jpelaa commented Sep 27, 2019

An error was thrown: "Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. "

The error was thrown at hi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:61172)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:256084
at Vo (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:256125)
at oi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:58828)
at Jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:103390)
at vc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89163)
at Ac (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89088)
at ac (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:86037)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:45275
at n.unstable_runWithPriority (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:3691)

@threepointone
Copy link
Contributor

The error at the link is clear about the error.

This issue has no other information, so I’m going to close it. Happy to discuss if you can share more details.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

@jpelaa - Seems like this issue might be the same as is being reported in #16925 and #16926.

It's been closed since it doesn't provide much info. It would be helpful though if you were able to fill in some of the missing details:

  • What operating system and browser/version are you using?
  • What were you doing when this error happened? (Is it happening for a specific website? or after you've clicked a specific button?)

I am not able to reproduce the error locally and would greatly appreciate help in figuring out how to.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 28, 2019

4.1.2 has just been published to NPM and uploaded to the Chrome+Firefox stores with a fix for this issue (still assuming it is the same as was reported in #16926 and #16925). Sorry for the inconvenience.

@jpelaa
Copy link
Author

jpelaa commented Sep 28, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants