This was fixed when I upgraded my react and react-dom versions from 17.0.1
to 18.3.1
.
1 Like
This was fixed when I upgraded my react and react-dom versions from 17.0.1
to 18.3.1
.