useScreens on Android swallows all Touchable onPresses on transitioned screen

[dested]

When using FluidNavigator, if I have react-native-screens linked and use'd, when I transition from Page1 to Page2 I can not tap anything. It seems the ScreenContainer that is overlaid on top is capturing my clicks. Interestingly, all of my pan gestures work on Page2, but no onPress's make it through. If I remove useScreen() it works flawlessly, and this behavior is only affecting android (api 28, but I doubt that matters).

Any thoughts?

[tuvshinbatgeru]

Same issue appears.

RN-0.59.9
Fluid-0.3.2

[tuvshinbatgeru]

@chrfalch any advise

[tuvshinbatgeru]

As @dested mentioned above removing useScreen() works fine.

[jrwpatterson]

is there anyway of fixing it so we can use use screens?

…

On Thu, Jun 20, 2019 at 12:25 PM Tuvshinbat Gansukh < ***@***.***> wrote: As @dested <https://github.com/dested> mentioned above removing useScreen() works fine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#197?email_source=notifications&email_token=AEKKMOA6FFNSSNNQZOCKWGTP3LTAVA5CNFSM4HWPSDCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDZYUQ#issuecomment-503815250>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEKKMOGUER3L4S3TJAVI6ILP3LTAVANCNFSM4HWPSDCA> .

[chrfalch]

I don't have any advice here - could anyone help and see? We've had the same issue with the latest version of screens so we are using "^1.0.0-alpha.16" in our projects - and we can verify that it works with this version. There is also an issue in the react-native-screens repo about this: software-mansion/react-native-screens#61

[vinceprofeta]

@chrfalch Do you know if this has been resolved?

[emeraldsanto]

Disabling touch events during transition is by design but I found a way to enable them (although it requires to edit native code) and posted it on a react-native-screens issue here.

[matthias-pichler]

I have the same issue