You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iOS: _UIFloatingBarContainerView counts as an occluder, so press/fill refuse everything above the tab bar #2996
On an iOS simulator, press and fill refuse every element above the tab bar of a React Native app with:
Error (COMMAND_FAILED): Selector label="Add plant" is covered by another visible element and cannot be tapped safely
Nothing covers those elements on screen, and a coordinate press <x> <y> at the element's centre works. The node that counts as covering them is a full-screen UIKit container, _UIFloatingBarContainerView, which touches pass through. This looks like the iOS counterpart of #1806, where contentless full-screen containers counted as occluders on Android.
Repro
agent-device 0.21.15 (also 0.20.10), iPhone 18 Pro simulator, driven through agent-device proxy
App: an Expo SDK 57 app in Expo Go, with JS bottom tabs (expo-router/js-tabs). It's the example app from avas-app/agent-bridge, but any screen with content above a tab bar should do.
agent-device open host.exp.Exponent "exp://<metro-host>:<port>" --platform ios --device "<sim>"
agent-device press 'label="Add plant"'# covered
agent-device fill 'id="plant-name"'"Fern"# covered (on the next screen)
agent-device find "Plants, tab" click # works: the tab bar sits outside the container
agent-device press 380 118 # works: same button by coordinates
snapshot -i marks every content node [covered].
Evidence
From snapshot --raw, the container is a sibling above the app content, full screen apart from the tab bar, and reported hittable:
The content it "covers" is its sibling subtree at the same depth, with the same frame (0,0,402,791). The tab bar (y: 791) is outside the container's frame, which is why tab presses work.
Expected
A container with no content of its own that passes touches through (here _UIFloatingBarContainerView, possibly other _UI*Container* views) shouldn't count as an occluder. Or press/fill could fall back to the element's frame centre, the way a coordinate press works today.
Workaround
Look up the rect with get attrs <selector> --json and press/fill its centre by coordinates.
Activity
crockalet commentedon Sep 27, 2026
Runtime: reproduced on the iOS 27.0 simulator runtime (24A434). I haven't tried other runtimes.
refactor(snapshot): own the sibling-sized chrome rule in its own module
test(snapshot): split the sibling-sized-chrome family out of the occl…
fix(snapshot): stop sibling-sized chrome containers from covering the…
Merge remote-tracking branch 'origin/main' into migrate/doublespeed-p…
fix(snapshot): stop a SwiftUI toolbar host from covering the sheet it…