Call willMoveToWindow before navigating with react-navaigation about react-native-screens HOT 6 CLOSED

It appears that the way this is normally handled on iOS is by using willMoveToWindow and/or didMoveToWindow

When using UINavController, willMoveToWindow triggers with nil window when the animation starts. What happens under the hood is that UINavController then immediately remounts the view and only unmounts it when the animation is over.

I went ahead and attempted to implement that behavior in ScreenContainer (apparently we can't use UINavController directly for reasons). If you have some time please try it from my branch here: https://github.com/kmagiera/react-native-screens/tree/move_window_events

The patch is here -> master...move_window_events

from react-native-screens.

I made a minimal working example here: https://github.com/tychota/BugInputAcessoryView

• My bug: https://github.com/tychota/BugInputAcessoryView/tree/master
• The fix of the biggest bug, thanks to RN : tychota/BugInputAcessoryView#2
• The try to fix the bug with the patch of @kmagiera : tychota/BugInputAcessoryView#1 (sadly not working)

from react-native-screens.

I went ahead and attempted to implement that behavior in ScreenContainer (apparently we can't use UINavController directly for reasons). If you have some time please try it from my branch here: https://github.com/kmagiera/react-native-screens/tree/move_window_events

Can you detail a bit the reason ? Too much teasing for my curiosity :)

from react-native-screens.

Closing this as of #47 – the updated version will be published soon. Please try it out and reopen if the problem persist

from react-native-screens.

I will definitivly try. Thank you sir.

from react-native-screens.

Was a fix for this released? I'm having a bit of trouble following the convo here (I don't know anything about native dev). We're experiencing the exact same problem with the InputAccessoryView rendering a second or so after the screen transition ends. It works ok in regular react-navigation v5, so that's a fallback for now, but it would be great if we could use react-native-screens instead!

from react-native-screens.