Topic autocomplete missing part of touch target on iOS

[namse]

Hi. Very recently when I tab the topic, it just ignores my input.

Upload.from.GitHub.for.iOS.MOV

I'm not sure why it happened.

[namse]

I found that it only happened when I click left side of topics. I guess maybe resolved mark area makes some trouble.

[gnprice]

Thanks @namse for the report!

I reproduce the issue. Specifically:

• I see this on iOS (an iPhone 7 running iOS 15.6.1), but not on Android (a Pixel 4 running Android 12.)
• The symptom is: when I try to select a topic from that autocomplete popup by tapping somewhere near its left edge -- in about the region indicated by the red box in your comment -- it doesn't work. Instead, it behaves as if I'd tapped outside the popup entirely, to dismiss the whole compose box.
• On the other hand, if I tap anywhere else in the popup, it works fine -- the topic I tapped on gets selected.

I think the cause is not likely to be related to the resolved-topic checkmark. The symptom seems to be the same on topics that don't have that, and even when none of the topics in the list have it.

[gnprice]

OK, and with some further testing:

• I reproduce the issue on v27.191, the latest.
• I don't reproduce the issue on v27.190, the previous version.

We sent v27.191 to all users on 2022-09-08, a few days before this issue was filed. So that fits very neatly with the mention of it happening "very recently".

@chrisbobbe would you take a look at debugging this? I think the next step is to bisect to find where the regression happened (or if you have a guess as to what caused the issue, then to check that guess directly.)

[chrisbobbe]

Thanks for the report and video/screenshot, @namse, and thanks Greg for the investigation!

A git rebase has led me to 3edc37a as the offending commit; I plan to investigate soon.

[chrisbobbe]

It appears that the react-native-gesture-handler upgrade in that commit was a factor, by changing React Navigation's behavior so that it closes the keyboard for the swipe-right-to-go-back gesture at the moment you press the screen, instead of when you actually start swiping.

I expect a fix in @react-navigation/stack 6.1.0, from commit react-navigation/react-navigation@5a19877. I did a quick manual cherry-pick of that commit (it's a one-line change) in node_modules at main and the symptom resolved.

Greg, do we think we could take that @react-navigation/stack 6.1.0 upgrade soon, or should we look at other options, like examining the reason for the gesture-handler upgrade for a possible revert, etc.?

[gnprice]

We just had another report of this issue.