fix(ios): keep non-draggable sheets from being swiped away

[maxlapides]

Summary

With draggable={false}, the user can't drag or resize a sheet, but on iOS pulling down on its scrollable still dismisses it when dismissible is true. UIKit asks presentationControllerShouldDismiss: both for that scroll-edge pull and for a tap on the dim, and TrueSheet answered with dismissible alone.

A non-draggable sheet now refuses a dismissal while a pan is under way, so it can't be swiped or pulled away. Tapping outside it still dismisses it, and dismiss() is unaffected. The refused pull isn't reported as onDismissAttempt, since the sheet is dismissible.

Draggable sheets and dismissible={false} sheets behave as before.

presentationControllerShouldDismiss: is the same on v3, and the fix applies there too, minus the onDismissAttempt part (v3 doesn't have that event). Happy to open the v3 backport.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Test Plan

Bare example, iPhone 17 Pro simulator (iOS 26.5). Locally, the map screen's ScrollView sheet got draggable={false} and lost its refresh control, so a pull at the top reaches the sheet.

main:

• Before: pulling the list down from the top dismisses the sheet.
• After: the same pull, and a fast one from the header, leave it presented. Tapping above the sheet dismisses it.
• onDismissAttempt doesn't fire for the refused pull. With dismissible={false} added, the same pull fires it as before.
• Prompt sheet (draggable): still swipes away.

v3 (3.11.18), same change without the onDismissAttempt part:

• The pull leaves the sheet presented, and tapping above it dismisses it.

Checklist

• I tested on iOS
• I tested on Android
• I tested on Web
• I updated the documentation (if needed)
• I added a changelog entry (if needed)

[vercel]

@maxlapides is attempting to deploy a commit to the lodev09 Team on Vercel.

A member of the Team first needs to authorize it.

[lodev09]

Thanks @maxlapides! Verified on iOS 27: the pull is refused, the dim tap still dismisses, and the refused pull doesn't fire onDismissAttempt.

Pushed one fix (0e9d5ce): _refusedPanDismiss could go stale. UIKit asks shouldDismiss when a pull starts but only calls didAttemptToDismiss if the pull goes far enough, so a short pull left the flag set. If dismissible then flips to false (unsaved changes), the next pull's onDismissAttempt gets swallowed. It also survives re-presenting, since the controller is reused.

Repro: draggable={false}, short pull at the top of the list, set dismissible={false}, full pull → no onDismissAttempt.

The flag is now set on every shouldDismiss call.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
react-native-true-sheet	Ready	Preview	Oct 15, 2026 2:48pm UTC