Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

iOS: `_UIFloatingBarContainerView` counts as an occluder, so press/fill refuse everything above the tab bar

Aperta
  • Qualcosa non va?
#2,996 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, react-native, typescript
Ambito
mobile-dev, testing

Direzione di ricerca

Start by tracing the press and fill entry points using the reproduced selectors and the snapshot --raw output. Compare the iOS occlusion behavior with the Android case in #1806, and use the coordinate press workaround as a baseline. Done means content above the tab bar is no longer rejected when the full-screen container passes touches through, while genuine occlusion remains protected.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

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:

{"index":122,"parentIndex":11,"type":"Toolbar","role":"_UIFloatingBarContainerView","label":"Toolbar","identifier":"Toolbar","rect":{"x":0,"y":0,"width":402,"height":791},"enabled":true,"depth":12,"hittable":true}

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.

Lingua principale
TypeScript
Stelle
4.7k
Fork
304
Merge medio
11h 31m
PR unite (30g)
513

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.