Closed ChanghyeonYoon closed 11 hours ago
Related Issue #3184 #3206
Hi @ChanghyeonYoon! First of all, thank you for submitting this PR. Unfortunately, this is not a solution that we want to implement, so I have to close it.
I don't know the exact reason for the absence of the handler
The fact that handler doesn't exist is connected to StrictMode. The thing is, if you enable StrictMode in your application, renders
and effects
will be called twice. For some reason (we are yet to find out why), order of operations on iOS when new architecture is enabled is different than on the old one. In other words, handler is dropped, and then checked if it exists. This will fail, but for now we don't know what causes this difference.
Description
I don't know the exact reason for the absence of the handler, but it should work fine if you change it to that code. I think it's probably a flow issue when using React Native 0.76 New Architecture with React Navigation v7. Anyway, you can change the code to the following and it should work fine.
Test plan