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

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

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

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
android, github-actions, react-native, typescript
Domaine
ci-cd, mobile-dev, testing

Piste de recherche

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.

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

Description

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)
Langage dominant
TypeScript
Étoiles
552
Forks
53
Merge moyen
2 j 20 h
PR mergées (30 j)
17

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

Toutes les issues de callstack/react-native-brownfield

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.