@react-navigation/core@7.0.0-alpha.5 breaks SSR

[jkhaui]

Hi,

I have a project which uses the latest v7 alpha build of @react-navigation/native, along with a custom stack navigator fully working with SSR using react-native-web.

I started seeing the following error in my browser console a few days ago but it took me until now to make the connection to @react-navigation/core:

Sorry it’s not really feasible to provide a repro because I've already spent enough time debugging this. Just wanted to raise awareness in case it affects other users, given it’s an opaque error message which can take hours to trace to the source. Hopefully someone can work out what's going on internally with this information and push a fix.

For now, the best evidence I can provide that the latest alpha release is breaking SSR are these screenshots which demonstrate the issue being fixed after locking @react-navigation/core to 7.0.0-alpha.4 instead of using the latest alpha.5 release:

If I had to take a complete guess at the cause of this behaviour, it would probably be the addition of some impure logic within useEffect/render which breaks the idempotent guarantees required by concurrent React.
One interesting thing is the error goes away completely when I remove the <Freeze/> component from react-freeze I use to wrap all my screens.