Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#3,992 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ios, react-native, typescript
Área
mobile, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
5.1k
Forks
339
Merge medio
12 h 53 min
PR fusionados (30 d)
644

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.