selector in useSelector called one more time after forceUpdate inside hook

What is the current behavior?

When state changed, selector recomputes, and value sets into latestSelectedState. Component will re-render, and selector recomputes again, but its value already in latestSelectedState.current

(selector is arrow function - const data = useSelector((state) => state.data);)

What is the expected behavior?

Selector recomputes once

I can open PR to fix this, but I don’t know, may be selector specially calls twice for some reasons

[markerikson]

@phantomcosmonaut no, that shouldn’t have anything to do with this issue. This is about a selector re-running when the component is already rendering. What you’re describing is a store subscription causing a component to render in the first place.

If you’re seeing problems with React-Redux and Suspense, please file a new issue with a reproduction so we can look into it.

[phantomcosmonaut]

Hey, I was using Suspense and a custom hook to render components asynchronously with async data fetching redux actions and I seem to have run into an issue directly related to this thread. I get the error Cannot update a component ('IdentityVerificationScreen') while rendering a different component ('RenderSuspender'). To locate the bad setState() call inside 'RenderSuspender' which takes me to the forceRender call from useSelector hook. Do you think the update in 7.2.4 will solve this issue and when can I expect to see the new version released? Thanks!