fix: footer touch swallowing and safe area inset bugs

[isaacrowntree]

Summary

• iOS: Footer buttons/touchables don't respond to taps because Fabric's touch system hit-tests using stale Yoga frames while AutoLayout has moved the footer to a different position. Fix: give the footer its own RCTSurfaceTouchHandler so it has an independent coordinate space rooted at its actual frame.
• Android: Footer touches dispatched to JS twice — once by dispatchTouchEvent routing to footer's RootView, and again by onInterceptTouchEvent/onTouchEvent on the ViewController. Fix: skip JS dispatch in the ViewController when the touch is in footer bounds.
• iOS: Footer ignores safe area insets — content renders behind the home indicator on notched iPhones. Fix: pin to safeAreaLayoutGuide.bottomAnchor instead of bottomAnchor.
• Android: Footer renders behind the navigation/gesture bar. Fix: subtract bottomInset in positionFooter (skipped when keyboard is visible since currentKeyboardInset already accounts for it).

Root cause (iOS touch bug)

TrueSheetFooterView.updateLayoutMetrics skips [super updateLayoutMetrics:...] after initial layout (line 93-96), so the Yoga frame goes stale while AutoLayout moves the view to the container bottom. RCTSurfaceTouchHandler on the container hit-tests using Yoga frames → can't find the footer at its visual position → touches dropped or delivered to the wrong component.

The fix mirrors the existing Android pattern where TrueSheetFooterView implements RootView with its own JSTouchDispatcher — on iOS we achieve the same by giving the footer its own RCTSurfaceTouchHandler.

Test plan

• Tap Button and TouchableOpacity in footer on physical iOS device — taps register
• Tap footer buttons on physical Android device — taps register, no double-press
• Footer content doesn't render behind home indicator (notched iPhone)
• Footer content doesn't render behind gesture bar (Android)
• Keyboard avoidance still works — footer moves up with keyboard
• Test with dismissible={false}
• Test at different detent sizes (small, medium, full)
• Test with and without insetAdjustment="automatic"

Reproduction app: https://github.com/isaacrowntree/truesheet-touch-repro

🤖 Generated with Claude Code

[vercel]

@isaacrowntree is attempting to deploy a commit to the Jovanni's projects Team on Vercel.

A member of the Team first needs to authorize it.

[lodev09]

Thanks @isaacrowntree!

Do you have a repro from a fork of this repo that I can replicate on my end prior to your changes? I want to test this properly.

[isaacrowntree]

Hey @lodev09! Here's a repro branch on my fork of this repo:

isaacrowntree/react-native-true-sheet@repro/footer-touch

It adds a FooterReproSheet to the Test Screen in the example app with three variants covering all the test cases:

Button	What it tests
Footer Repro	Tappable button + TextInput in footer (touch bug + keyboard avoidance)
Footer (dismissible=false)	Same footer with dismissible={false}
Footer (insetAdjustment=auto)	Same footer with insetAdjustment="automatic"

All three use detents={['auto', 'medium', 'large']} so you can test at different sizes.

On a physical device before the fix:

• iOS: footer button taps are silently dropped, TextInput can't be focused
• Android: footer button taps fire twice (double alert)
• Both: footer renders behind home indicator / gesture bar on notched devices

The existing BasicSheet footer is also made tappable for a quick sanity check.

I also rebased this PR on latest main so the conflicts are resolved.