Internal React warning when using recoil in stable react releases and not experimental

[incepter]

I bootstraped a react app using create-react-app, then added recoil and just pasted the code from the website demo.

When the app renders for the first time, an internal react warning in console is shown:

Warning: Cannot update a component (`he`) while rendering a different component (`CharacterCount`). To locate the bad setState() call inside `CharacterCount`, follow the stack trace as described in https://fb.me/setstate-in-render
    in CharacterCount (at App.js:31)
    in div (at App.js:29)
    in CharacterCounter (at App.js:7)
    in RecoilRoot (at App.js:6)
    in App (at src/index.js:7)
    in StrictMode (at src/index.js:6)

Updating react dependencies to the experimental ones solved the warning.

PS: the issue doesn't occur with react^16.12 but only with ^16.13.1

Here is a codesandbox demo

So, should we use recoil only with the experimental react release ?

[incepter]

Here is the full stack trace.

I will continue through the tutorial to know the basics and advanced stuff of recoil, if this is not solved I wish I work on it.

[incepter]

I figure out that this warning was added after the experimental and 16.12 releases.

[davidmccabe]

Thanks for reporting, I'm currently looking into this.

[Xiphe]

facing similar issues on

"react": "0.0.0-experimental-33c3af284",
"react-dom": "0.0.0-experimental-33c3af284",
"recoil": "0.0.7"

[kalysr]

facing similar issues on

    "react": "^16.13.1",
    "react-dom": "^16.13.1",
    "react-scripts": "3.4.1",
    "recoil": "^0.0.7"

[acutmore]

Possible duplication of #12

[incepter]

Possible duplication of #12

Yes absolutely a duplicate, didn't notice it.

I do not know how to flag this issue as a duplicate.

[drarmstr]

Duplicate of #12