getsentry / getsentry/sentry-java

NoSuchMethodError in SentryTraced during Compose composition

Aperta
#5,732 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Android Platform: Java
Lingua principale
Kotlin
Stelle
1.4k
Fork
478
Merge medio
2g 23h
PR unite (30g)
67

Descrizione

## Symptoms

`NoSuchMethodError` is thrown at the entry of the public `SentryTraced` composable during Jetpack Compose composition.

* **Crash location:** `io.sentry.compose.SentryComposeTracingKt.SentryTraced(SentryComposeTracing.kt:72)` — the function header, before any body statement executes.
* **Trigger path:** normal composition (`setContent` → `Recomposer.composeInitial` → `doCompose` → `ComposableLambdaImpl.invoke` → `SentryTraced`).
* **Handling:** unhandled, crashes the app via `UncaughtExceptionHandler`.
* **Exception detail message:** not available — stripped by SDK crash detection (`error.value` is `null` on all events), so the exact missing method name is unknown.

## Scope / frequency

* 151 occurrences, 2 users impacted.
* First seen 2026-03-19, still ongoing (last seen 2026-07-07).
* Spans multiple SDK versions: 8.33.0, 8.40.0, 8.43.1, 8.47.0 (not a regression tied to one release).
* Android only. Every event is on an Android emulator (`sdk_gphone64_arm64`, `simulator: true`, `userdebug` build, Android 14).

## Reference

* Sentry issue: SDK-CRASHES-JAVA-48AR — [https://sentry.sentry.io/issues/SDK-CRASHES-JAVA-48AR]()

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start at SentryComposeTracing.kt:72 and trace the normal setContent → Recomposer.composeInitial → doCompose → ComposableLambdaImpl.invoke → SentryTraced path. Reproduce the crash on the reported Android emulator configuration and compare the listed SDK versions to identify the missing method and establish a fix that prevents the public composable from throwing NoSuchMethodError.

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

Valutazione

Stack tecnologico
android, kotlin
Ambito
mobile
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Da chiarire
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.