Wojciech Lewicki
Wojciech Lewicki
It would be best if you could provide a repo with a reproduction of the issue so we could work on it, it is hard to say much without it...
I think we will not go this way with custom transitions. After we release SET(https://github.com/software-mansion/react-native-screens/pull/1591), I think we can extend the API to be able to animate whole screens with...
I pushed the work I started some time ago concerning the shared element transitions: https://github.com/software-mansion/react-native-screens/pull/1089. It is just a draft version with some attempts to make the basic scenarios work...
cc @kacperkapusciak
Have you tried to apply this suggestion: https://github.com/software-mansion/react-native-screens/issues/111#issuecomment-757518915 ? It will make the previous screen stay in the native view hierarchy after navigating forward, so the flicker should not be...
Yeah, the problem comes from the detaching/attaching process being connected to `Animated.Value` on the side of `react-navigation` (see how it is resolved around here: https://github.com/react-navigation/react-navigation/blob/4c5805867ce946d99ba17f71b4d6086bb8751262/packages/stack/src/views/Stack/CardStack.tsx#L580). Maybe there is a way...
IIRC, the exact problem comes from this line: https://github.com/react-navigation/react-navigation/blob/4c5805867ce946d99ba17f71b4d6086bb8751262/packages/stack/src/views/Stack/CardStack.tsx#L595 where we switch the value of `isScreenActive` not exactly when the animation ends, but `1-EPSILON`. I cannot remember why exactly was...
Unfortunately I don't know. If you don't spot any new issues with the decreased value, you can submit a PR with such a change.
@nickyleach can you try and use the solution proposed here: https://github.com/software-mansion/react-native-screens/issues/645#issuecomment-712199841?
@savelichalex I am afraid the change proposed here was rather a quick workaround, not a solution to the problem, and so it might not be ever merged in order not...