Skip to main content
GoodFirstPicks
DashboardIssuesReposLeaderboard

GoodFirstPicks by Leaveitblank © 2026

CreatorRequest a RepoPrivacy PolicyTerms of Service
"Should not already be working" in Firefox after a breakpoint/alert | GoodFirstPicks

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

facebook/react 128 comments 1mo ago
View on GitHub
mediumopenScope: somewhat clearSkill match: maybeReactJavaScriptTypeScript

Why this is a good first issue

Error occurs in production but cannot be reliably reproduced for debugging.

AI Summary

Users report 'Should not already be working' errors in production across multiple browsers and React versions, but no one can reliably reproduce the issue locally. The error suggests an internal React bug, but without reproduction steps or clear patterns, investigation will be challenging.

Issue Description

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.

GitHub Labels

Type: BugDifficulty: mediumType: Needs Investigationgood first issue

Want to work on this?

Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!

Risk Flags

  • reproduction difficulty
  • multiple browser/OS combinations
  • potential memory issues
Loading labels...

Details

Points10 pts
Difficultymedium
Scopesomewhat clear
Skill Matchmaybe
Test Focusedno