Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#499 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 4 Tagen

@KisaneNeko arbeitet bereits daran.

Seit 16.10.2026.

  • #501 von @KisaneNeko — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
android, github-actions, react-native, typescript
Bereich
ci-cd, mobile-dev, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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)
Vorherrschende Sprache
TypeScript
Sterne
552
Forks
53
Ø Merge
3 T. 13 Std.
Gemergte PRs (30 T.)
16

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus callstack/react-native-brownfield

Alle Issues in callstack/react-native-brownfield

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.