Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Limrun iOS: the iOS 26 tab bar is one empty node, its tabs are missing from the snapshot

Offen
  • Stimmt etwas nicht?
#3,992 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
ios, react-native, typescript
Bereich
mobile, testing

Rechercherichtung

Read ios-snapshot-adapter.js and trace captureLimrunIosSnapshot, then compare its Limrun tree handling with collapsedTabFallbackNodes and shouldExpandCollapsedTabContainer in RunnerTests+SnapshotAcquisition.swift. Reproduce the collapsed group tab bar on iOS 26 and determine whether Limrun’s elementTree exposes enough information to resolve its tabs. Done means the Limrun snapshot includes separately accessible tab nodes, matching the simulator behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

What happens

On a Limrun iOS instance, an iOS 26 UITabBar comes out of snapshot as one empty node. None of its tabs appear anywhere in the tree, so getByText("Notes") / press by label never finds a tab, and agents fall back to raw coordinates.

The same app on a local iOS 26.4 simulator, read through agent-device's own XCUITest runner, lists every tab.

Versions

  • agent-device 0.21.22. The Limrun path in 0.21.32 still reads client.elementTree() with no tab-bar handling.
  • e2e 0.18.0 / @e2e-dev/mobile 0.10.0
  • iOS 26.4. Limrun instance: os-version/26.4, viewport 402×874.
  • App: Expo SDK 57, tabs from expo-router/unstable-native-tabs (a native UITabBarController), four tabs plus a role="search" tab.

Limrun (producer: limrun-ios-tree)

#root screen
 #n5763 application "Notez-Test"
  #n5764 generic-element "Notez, Get Pro, Search, Settings"
  ...
  #n5775 generic-element "Start Recording"
  #n5776 group "Tab Bar"
  #n5777 text "07:17"

Local simulator, same build (agent-device open … --platform ios)

@e11 [tab-bar] "Tab Bar"
@e12 [button] "Home"
@e13 [button] "Notes" [selected]
@e14 [button] "Calendar"
@e15 [button] "AI Chat"
@e16 [button] "Create Note"

The simulator's accessibility service also lists the five tabs as separate buttons inside the bar's frame.

Where it seems to come from

  • ios-snapshot-adapter.js (captureLimrunIosSnapshot) builds the snapshot straight from Limrun's elementTree.
  • The Apple runner already handles a tab bar whose snapshot has no children: collapsedTabFallbackNodes / shouldExpandCollapsedTabContainer in RunnerTests+SnapshotAcquisition.swift.
  • That handling never runs on the Limrun path. Limrun's tree also gives the bar type group, not tab bar.

Ask

Either of these would fix it:

  • Resolve the tabs on the Limrun path too, as the runner does for a collapsed tab container.
  • If the gap is in Limrun's elementTree itself, raise it with Limrun.

Until then, tabs on Limrun can only be reached by coordinates.

Vorherrschende Sprache
TypeScript
Sterne
5.1k
Forks
339
Ø Merge
12 Std. 53 Min.
Gemergte PRs (30 T.)
644

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus callstack/agent-device

Alle Issues in callstack/agent-device

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.