Tymoteusz Boba

@efstathiosntonas One more question, have you tried listening to screen lifecycle events (transitionStart/transitionEnd with changing the `closing` parameter)? I can observe they should work in correct order, but maybe you...

@efstathiosntonas Yeah! On every screen, you can define `listeners` prop that will serve as an object of your desired listeners. We've got two interesting events there: transitionStart and transitionEnd (each...

@arasrezaei Hey! This PR is currently blocked with the issue about the wrong order of disappearing screens from the native-stack. Previously, while the next screen was sending `onWillAppear` events after...

@kirillzyusko Yeah, that's correct - from what I can see is that Samsung/OPPO/any other distros are oftenly overriding the transitions to the custom one. I think the best source to...

Hey hey @arasrezaei, unfortunately this PR is blocked by the wrong order of incoming events related to screen mounting/unmounting, which leads to the breaking change we definitely don't want by...

This looks like an issue with screen transitioning and draw ordering - we may need to check if [this commit](https://github.com/software-mansion/react-native-screens/commit/6eb587abd398df12d67894d53e72590c4f17921f) may cause this 😕

Yeah, most likely that's because of the transition duration. However, what's even stranger, I can see that on both versions of screens this lag exists (it's shorter on 3.29.0, though)....

Hi @lovegaoshi! Could you check if installing screens version from this branch: https://github.com/software-mansion/react-native-screens/pull/2110 fixes this issue?

@lovegaoshi hmm, I believe you need to do `yarn prepare` inside the node_modules/react-native-screens, since it's not automated now, because of yarn v4 😕

@WoLewicki since there's open issue on RN repo, addressing why did we open this PR, should we close this PR?