Tomasz Boroń
Tomasz Boroń
The work is continued here: https://github.com/software-mansion/react-native-screens/pull/3336
superseded by https://github.com/software-mansion/react-native-screens/pull/3248
Fixed by: https://github.com/software-mansion/react-native-screens/pull/3248 https://github.com/user-attachments/assets/02388ddb-6237-4fbd-ae67-05f37aa9b867
> Should we support this in 8.x or should I cherry-pick to 7.x only? cherry-picking it only to `7.x` is fine; for stack v5 we're planning to rewrite the logic...
Since `react-native-screens` were upgraded to `4.19` on the `7.x` branch, I'm setting this PR as ready. Please let me know if there are any further actions on my side.
> I think that we complicate things too much here. > > If the old solution is reliable (it is, right?) and the new one is only a refactor using...
@kkafar we have the same case in the stack v4: https://github.com/software-mansion/react-native-screens/pull/3368 , therefore I believe that we should land both, or rather, both should be moved to `on hold` state
> @t0maboro Let's move both to on-hold state. I think that we defeat the purpose currently by introducing two separate mechanism depending on version. Let's wait few weeks. ack
Switching to draft until we drop support for RN versions prior to 0.82
The issue is reproducible with the native application ```obj-c #import "ViewController.h" @interface ViewController () @property (nonatomic, strong) NSMutableArray *pressableViews; @end @implementation ViewController #pragma mark - Init - (instancetype)init { self...