Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#3,992 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
ios, react-native, typescript
Domaine
mobile, testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
5.2k
Forks
359
Merge moyen
12 h 48 min
PR mergées (30 j)
657

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstack/agent-device

Toutes les issues de callstack/agent-device

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.