Request to expose TouchUITapGestureRecognizer and provide a way to cancel TouchBehavior

[maonaoda]

sealed class TouchUITapGestureRecognizer : UIGestureRecognizer

Maui/src/CommunityToolkit.Maui/Behaviors/PlatformBehaviors/Touch/TouchBehavior.macios.cs

Line 91 in c1d2ee3

sealed class TouchUITapGestureRecognizer : UIGestureRecognizer

---

Request to expose TouchUITapGestureRecognizer and provide a way to cancel TouchBehavior

Background

In our iOS app, we override the system back gesture using a custom UIScreenEdgePanGestureRecognizer to implement customized navigation behavior.

However, when the current page uses CommunityToolkit.Maui TouchBehavior, a gesture conflict occurs between:

• the custom UIScreenEdgePanGestureRecognizer, and
• the internal gesture handling used by TouchBehavior.

This conflict makes it difficult to reliably handle the iOS edge-swipe back gesture when TouchBehavior is attached to a view.

Problem

Currently, there is no public way to detect or cancel an active TouchBehavior interaction.

Internally, TouchBehavior relies on TouchUITapGestureRecognizer, but this class is not public, and there is no exposed API that allows the application to cancel the touch interaction when another gesture (such as UIScreenEdgePanGestureRecognizer) takes priority.

As a result:

• The system or custom back gesture may be blocked or behave incorrectly
• Applications cannot coordinate gesture priority between UIKit gestures and TouchBehavior

Proposal

I would like to request:

1. Making TouchUITapGestureRecognizer a public class, and
2. Exposing a public method to cancel the current touch interaction used by TouchBehavior.

For example, an API similar to the following:

/// <summary>
/// Cancels the touch interaction.
/// </summary>
public void CancelTouch()
{
    if (!behavior.IsEnabled)
    {
        return;
    }

    HandleTouch(TouchStatus.Canceled, TouchInteractionStatus.Completed);
    isCanceled = true;
}

This would allow applications to:

• Cancel TouchBehavior explicitly when a higher-priority UIKit gesture is recognized
• Avoid gesture conflicts with UIScreenEdgePanGestureRecognizer
• Implement more predictable and platform-consistent navigation behavior on iOS

Benefits

• Better interoperability between MAUI behaviors and native UIKit gestures
• Avoidance of gesture conflicts in advanced navigation scenarios
• Greater flexibility without requiring developers to reimplement touch handling logic

I believe this would be a valuable improvement for apps that need fine-grained control over gesture coordination on iOS.