Description
I am working on a mobile app, and I have a XAML element with a Swipe Gesture Recognizer added and listening for right swipes. Nested deep inside of this structure is a CollectionView that scrolls horizontally. When a user scrolls on the CollectionView on an Android device, the Border's gesture is not triggered. On iOS, it is triggered. This is different and undesirable.
Figure A.
var swipeGesture = new SwipeGestureRecognizer
{
Direction = SwipeDirection.Right,
Threshold = 200
};
swipeGesture.SetBinding(SwipeGestureRecognizer.CommandProperty, nameof(MyScreen.NavigateBackCommand)); // Change as needed for replication. It can be as simple as a function that logs when it is called.
MyBorder.GestureRecognizers.Add(swipeGesture);
Steps to Reproduce
- Create a new MAUI app with a blank page
- Add and name a that covers the whole screen
- Add Figure A to the code behind
- Create and fill a inside of the Border
- Run on iOS and Android
- Note that the GestureRecognizer's bound command is triggered by swiping right inside of the collectionview on iOS (bad), but not on Android
Link to public reproduction project repository
No response
Version with bug
10.0.20
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 26 and up
Did you find any workaround?
No response
Relevant log output
Description
I am working on a mobile app, and I have a XAML element with a Swipe Gesture Recognizer added and listening for right swipes. Nested deep inside of this structure is a CollectionView that scrolls horizontally. When a user scrolls on the CollectionView on an Android device, the Border's gesture is not triggered. On iOS, it is triggered. This is different and undesirable.
Figure A.
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
10.0.20
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 26 and up
Did you find any workaround?
No response
Relevant log output