SFTabView: EnableSwiping option makes tapping difficult on Android 15+

[DominikTulak]

Description

When using SFTabView with the EnableSwiping option enabled, we've observed that on Android 15+ devices, taps or clicks are harder to register than on Android 14.

Specifically, when tapping a button displayed within a tab, the user has to tap very carefully without moving their finger at all. If the finger moves even slightly, the click is not registered; instead, it seems to be interpreted as a very small swipe. This results in a typical user being unable to click buttons reliably.

If I tap without any finger movement, the click is registered correctly. However, most users naturally move their finger slightly during a tap, causing their clicks to be missed.

This behavior does not occur on Android 14 or earlier. On those versions, a click with slight finger movement is registered as expected.

I was able to reproduce this behavior using the TabViewGettingStarted sample by simply enabling the EnableSwiping option. I used the Syncfusion.Maui.TabView NuGet version 31.2.16.

---

Devices on which we reproduced the issue:

• Samsung Galaxy A55 5G running Android 15 and Android 16
• Samsung Galaxy S21FE running Android 15

Devices on which TabView works as expected:

• Samsung Galaxy A41 running Android 12
• Xiaomi 11T running Android 14

---

Based on our testing, the issue also does not appear on any iOS device.
Here’s a video demonstrating the issue

Steps to Reproduce

Please describe the steps to reproduce the behavior you've observed, along with what you expected to happen and what actually occurred.

1. Add EnableSwiping="true" to an SFTabView in your project.
2. Ensure there are at least two tabs, and each tab contains buttons.
3. Run the application on a device with Android 15 or newer.
4. Attempt to tap the buttons within any tab.

Expected behavior:
Tapping a button should register the click, even if the finger moves slightly during the tap, as it does on Android 14 or older and on iOS.

Actual behavior:
On Android 15 or newer, the click is only registered if the finger does not move at all. Any small movement is interpreted as a swipe, causing the button tap to be ignored.

.NET Version

.NET 9.0

Version with bug

1.0.7

Is this a regression from previous behavior?

No, this is a new issue

Last Known Working Version

1.0.6

Affected platforms

Android

Affected Platform Versions

Android 15 and newer

Have you found a workaround?

We have not found a workaround that fully preserves the original behavior.

To maintain the ability to click buttons, we had to set EnableSwiping to false. To still allow users to swipe between tabs, we integrated MR:Gestures and handled the Swiped event manually by incrementing or decrementing TabView.SelectedIndex. This approach enables tab swiping, but does not provide the same smooth experience as the built-in EnableSwiping option.

With the original option, the tab content smoothly follows the user's finger during the swipe gesture. In our workaround, the gesture recognizer waits until the swipe gesture is complete, then switches to the selected tab - sometimes missing the swipe animation and instantly switching tabs instead. This results in a less fluid and less visually appealing user experience.

Relevant log output

[naveenkumar-sanjeevirayan]

Hi @DominikTulak,

We were unable to reproduce this issue on our end. However, based on the scenario you described, we have identified the possible cause and implemented a fix that is needed.

To fully resolve the issue, kindly apply the changes available in the below Pull Request (PR) from your side.

Please let us know once the changes are applied, or if you continue to face any issues.

PR - #317

Regards,
Naveenkumar S

[DominikTulak]

Hi @naveenkumar-sanjeevirayan

thank you for taking the time to investigate this issue and for your efforts in identifying a possible cause, even though you weren’t able to reproduce it on your end — we really appreciate it.

I’ve built the SyncFusion Toolkit from the provided branch and can confirm that the changes resolve the issue for us. While the buggy behavior is still present in version 1.0.8 on our side, using this branch fixes the issue and makes clicking work as expected.