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

Flaky Android Expo Detox E2E: native greeting never shows up / app drops Detox connection

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

Los mantenedores suelen responder en 3 días

@KisaneNeko ya está trabajando en esto.

Desde el 16/10/2026.

  • #501 de @KisaneNeko — abierto
  • #504 de @KisaneNeko — abierto

Evaluación

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

Línea de trabajo

Start by downloading the Detox Android artifacts from the linked failed CI runs and inspect logcat-full.txt for a crash or ANR around the reported failures. Compare logs from both failure modes and the Vanilla job to see whether they share a cause. Done means identifying and reproducing the root cause on the matching CI emulator; collecting tombstones is suggested as an additional diagnostic.

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

Descripción

The Detox E2E (AndroidApp - Expo XX) jobs keep failing on both Expo 57 and 58, on main and on PRs. Both tests in the suite fail together, so the job goes red each time it happens.

There are two ways it fails:

  1. The native greeting never shows up. In beforeAll, the app process starts (Android app process is up), but Hello native Android (Expo XX) never appears in UIAutomator. After ~90s it fails with Timed out waiting for UIAutomator to contain any of: Hello native Android (Expo 58), ....
  2. The app drops the Detox connection after opening the Expo RN screen. The greeting is fine, then Opening the Expo RN screen... → Detox can't seem to connect to the test app(s)!, which looks like the app crashed.

Also this one, where it lost the connection right after the process came up, before the greeting check finished: #487 e0f5940, Expo 57: https://github.com/callstack/react-native-brownfield/actions/runs/38458013604/job/115565183435

So my guess is the app is crashing in all of them, just at different moments. The failed jobs already upload the full host-side logcat (logcat-full.txt, added in #473) together with the other Detox artifacts (#466), in the detox-androidapp-<flavor>-<flavor>-android artifact. I haven't gone through those logs yet to confirm a crash.

The Android road test & E2E (AndroidApp - Vanilla) job fails the same way as (1): it waits for Hello native Android and all 4 tests time out. That one has failed on main d28810c, #494 and #487, so it might be the same root cause:
https://github.com/callstack/react-native-brownfield/actions/runs/38857242075/job/116831993012

To do:

  • go through logcat-full.txt from the failed runs' artifacts and look for a crash / ANR
  • consider also pulling tombstones (/data/tombstones) on failure (not collected yet)
  • try to repro locally on the same emulator image (API level / ABI as CI)
Lenguaje dominante
TypeScript
Estrellas
552
Forks
53
Merge medio
2 d 20 h
PR fusionados (30 d)
17

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/react-native-brownfield

Todos los issues de callstack/react-native-brownfield

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.