XCTest nightly: in-app back on the sole screen flakes with changed=yes

Abierto
  • ¿Algo no está bien?
#4,322 1 comentario 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
cypress, ios, typescript
Área
mobile, testing-qa

Línea de trabajo

Start with RunnerTests+NavigationTests.swift:65 and inspect the IN_APP_BACK_VISUAL_VERIFICATION capture comparison and the sole-screen test fixture. Compare consecutive captures to identify what changed after the tap, then determine whether the verification or fixture owns the fix. Done means the root cause is fixed with a deterministic test, or the test passes in five consecutive XCTest Nightly iPhone runs.

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

Descripción

bug

Purpose

testInAppBackOnTheSoleScreenReportsATapThatChangedNothingAsUnavailable fails intermittently in the XCTest Nightly iPhone leg on iOS 26.2.

Current behavior

The test fails at RunnerTests+NavigationTests.swift:65: "a top-leading tap on an app without a back control must not read as performed". The runner logs IN_APP_BACK_VISUAL_VERIFICATION … changed=yes. So two real screen captures differed after a tap that should change nothing.

Runs:

  • main nightly 42338987297 (2026-11-07): failed.
  • #4320 nightly 42390630488: passed.
  • #4320 nightly 42394725350: failed, the only failure in 665 tests.

Required behavior

  • Find what differs between the two captures, for example a status bar clock, a cursor blink, a transient overlay or an animation still settling.
  • Make the visual verification ignore changes that a tap cannot cause, or make the test fixture static. Fix it at the owner: the verification if it misreads product behavior, or the fixture if the test is the problem.
  • Don't retry the test or skip it.

Completion conditions

  • The test passes in 5 consecutive XCTest Nightly iPhone runs, or the root cause is shown and fixed with a deterministic test.
Lenguaje dominante
TypeScript
Estrellas
5.3k
Forks
377
Merge medio
13 h 58 min
PR fusionados (30 d)
654

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.