getsentry / getsentry/sentry-java

NoSuchMethodError in SentryTraced during Compose composition

未关闭
#5,732 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Android Platform: Java
主要语言
Kotlin
星标
1.4k
派生
478
平均合并
2 天 23 小时
30 天内合并 PR
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

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。