getsentry / getsentry/sentry-java
NoSuchMethodError in SentryTraced during Compose composition
- 主要言語
- Kotlin
- スター
- 1.4k
- フォーク
- 478
- 平均マージ
- 2日 23時間
- マージ済み PR(30日)
- 67
説明
## 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]()
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- android, kotlin
- 領域
- mobile
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 静か
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 35/100