getsentry / getsentry/sentry-java

NoSuchMethodError in SentryTraced during Compose composition

Ouverte
#5,732 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Android Platform: Java
Langage dominant
Kotlin
Étoiles
1.4k
Forks
478
Merge moyen
2 j 23 h
PR mergées (30 j)
67

Description

## 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]()

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

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

Évaluation

Stack technique
android, kotlin
Domaine
mobile
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.