"Should not already be working" in Firefox after a breakpoint/alert

**Do you want to request a *feature* or report a *bug*?** Bug **What is the current behavior?** I'm seeing "Error: Should not already be working" after upgrading to React 16.11 **Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?** This is exclusively happening on an older version of Chrome, 68.0.3440 on Windows 7 I was unable to reproduce this in a VM environment but our Sentry is getting littered with these errors. I know it's a long shot, but I wasn't able to find any information about this error anywhere, just a reference in the error codes file in react, so thought it would be a good idea to report this just in case. Curious if anyone has seen this.

Posted by gzzo on Nov 13, 2019, 4:35 PM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Proposal to Reorganize the Moderation Team and Review Moderation Policies
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0