Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#3,992 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@thymikee já está trabalhando nisso.

Desde 28/10/2026.

  • #4019 de @thymikee — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
ios, react-native, typescript
Domínio
mobile, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug in-progress ready-for-agent

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.

Linguagem predominante
TypeScript
Estrelas
5.2k
Forks
359
Merge médio
12h 43min
PRs com merge (30d)
666

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de callstack/agent-device

Todas as issues de callstack/agent-device

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.