-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Did not retain recoil value on render, or committed after timeout elapsed. This is fine, but odd. undefined #1034
Comments
same here! |
Also receiving the same error message. I rolled back to 0.2.0 |
Just installed recoil ^0.3.1 and getting this issue after following a basic setup tutorial. Everything works but just getting this console error, so it seems fine I guess. Just odd. |
I can confirm this warning occurs in my simple "counter" project with create-react-app (with typescript) + recoil. Warning disappears if the page is reloaded. However, despite the message, the recoil state value is retained after hot reload. I'm guessing maybe recoil doesn't check for hot reloads. |
I have this issue with react native and expo, recoil 0.3.1 |
We investigated this and will be removing the warning. It should be safe to ignore. (cc @davidmccabe) |
I encountered this warning today after switching to the latest experimental version of react. Additionally, the state variable wasn't updating when using useRecoilState. Downgrading to an earlier experimental version of react/react-dom fixed the issue. |
You can safely ignore this warning. Next point release will remove it. Sorry about this :( |
Removed in #1062 |
stilling facing this error in 0.3.1 update |
This was after |
I'm getting this error after React hot-reload, since I've updated Recoil to 0.3.0. I haven't noticed any issues in my app related to this, but console throws this every time. Don't know which part exactly is causing it, since it started after Recoil update, not in the development process.
I'm using latest create-react-app + react-app-rewired, RxJS, Recoil and Material UI.
The text was updated successfully, but these errors were encountered: