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

Diagnose recurring multi-minute Settings replay click in iOS Smoke

Aperta
  • Qualcosa non va?
#2,948 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
32/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, typescript
Ambito
mobile-dev, performance, testing-qa

Direzione di ricerca

Start with the 01-settings.ad replay and the exact-head iOS runs linked in #2936, #2937, and #2938. Inspect the existing request/session diagnostics around click General, then run a live iOS replay to identify the slow phase and whether the action occurred. Done means the phase evidence explains the delay and a focused fix or evidence-backed disposition removes the repeated cost without masking failure.

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

Descrizione

needs-triage

Purpose

Reduce a recurring multi-minute delay in the iOS Smoke Settings replay and determine whether its successful click General response reflects a completed interaction.

Evidence

Three independent exact-head PR runs on 2026-09-24 show the same pattern in 01-settings.ad: the first attempt reports step 3 click General as successful after 143.840 s, 191.076 s, or 165.128 s; step 4 then times out after 5 s waiting for About, Software Update, or the expected Settings text. The retry succeeds in 30.5 s, 23.6 s, or 14.8 s respectively.

The recorded replay timing establishes the delay and failed wait; it does not establish which internal click phase consumed the time or whether the tap landed. The #2936 failed wait request log includes a simulator-target-discovery-pending bridge fallback, but successful click requests did not retain equivalent phase diagnostics.

Required behavior

  • Attribute the click time to target resolution, snapshot/bridge acquisition, XCTest transport, tap synthesis, and post-action work using existing request/session diagnostics or narrowly scoped new timings.
  • Determine from a live failing attempt whether General was actually activated before reporting click success; repair the owning path if success can be reported without the action, or bound an optional pre-action probe beneath the operation it precedes.
  • Preserve the retry as failure containment while diagnosing; do not treat the retry as proof of click correctness.

Completion

  • A live iOS run captures enough phase evidence to explain the 143–191 s first-attempt clicks and the subsequent failed wait.
  • A focused fix or an evidence-backed infrastructure disposition removes the repeated multi-minute cost without hiding a failed action. Compare exact-head iOS runner time and replay step timing against the linked runs.

Depends on no current PR; this is separate from #2936's depth-frontier diagnostic.

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

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.