hook.js:608 React instrumentation encountered an error: Error: We are cleaning up async info that was not on the parent Suspense boundary. This is a bug in React. #84973
-
|
As of late, by just navigating around my app, I am randomly getting this error. Anyone knows why this is happening? 
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 11 replies
-
|
Hi, is there any change we could see this application? or have some insight into what's the app doing? |
Beta Was this translation helpful? Give feedback.
-
|
I also wonder if you see this error in incognito mode? Maybe it is related to the dev tools? |
Beta Was this translation helpful? Give feedback.
-
No, it's regular mode. I didn't change the app, it just appeared in past coupla new versions of Next.js. Let me disable the dev tools and check again... |
Beta Was this translation helpful? Give feedback.
-
Yea, it disappeared. So, dev tools are either bugged or some known issue with it. Thank you for the hint, @icyJoseph ! |
Beta Was this translation helpful? Give feedback.
-
|
Btw, the app in question is https://guildplanner.pro |
Beta Was this translation helpful? Give feedback.
-
|
what user journey triggered this error? I clicked around but nada. |
Beta Was this translation helpful? Give feedback.
-
|
Also started running into it all of a sudden. I didn't do any upgrades. next => 15.6.0-canary.31 |
Beta Was this translation helpful? Give feedback.
-
|
Does it also go away if you don't have the React Dev Tools. |
Beta Was this translation helpful? Give feedback.
-
|
huh! yes! then it seems like a react dev tools issue rather than next.js. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Please delete this, not useful info |
Beta Was this translation helpful? Give feedback.
-
|
This seem not to be an issue related to the react-dev-tools no more. |
Beta Was this translation helpful? Give feedback.
-
|
Noticed this recently as well. I'm upgrading our NextJS app from version 14 to version 16. This also included a React 18 to 19 upgrade as well as Radix and other tools. As usual when upgrading I expected to regression test, log and fix deprecations, etc... however this is an unusual error... "This is a bug in React", but is this tied to suspense usage or what? Really just looking for some accountability... is this NextJS, React, Dev Tools :) |
Beta Was this translation helpful? Give feedback.
-
|
Is there a solution that does not require disabling react-devtools? |
Beta Was this translation helpful? Give feedback.
I also wonder if you see this error in incognito mode? Maybe it is related to the dev tools?