fix(android): identify and correctly structure Java/Kotlin frames…

[supervacuus]

…in mixed Tombstone stack traces.

📜 Description

This PR adds:

• identification of platform="java" in mixed platform Tombstone stack frames
• restructuring of those platform="java" frames to the expected backend format (using module, function, and platform: "java" instead of package, function, instruction_addr as used for native frames)
• a snapshot test against the tombstone that checks the identification of Java frames and in-app doesn't regress

💡 Motivation and Context

This is a planned item of the "wrap-up" UI improvements in https://linear.app/getsentry/project/tombstone-support-android-0024cb6e3ffd/

It covers the SDK part of https://linear.app/getsentry/issue/ANDROID-265/improve-ux-for-mixed-stacktraces (getsentry/sentry#107318).

💚 How did you test it?

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[linear]

ANDROID-265 Improve UX for mixed stacktraces

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

Bug Fixes 🐛

• (android) Identify and correctly structure Java/Kotlin frames… by supervacuus in #5116

---

_{🤖 This preview updates automatically when you update the PR.}

[supervacuus]

While testing this manually, it became apparent that the SDK-level inApp detection and the one on the server disagree. See here: https://sentry-sdks.sentry.io/issues/7288803722/events/af5e7573571f4cd98616f947e081ad09/

In the event, only the JNI frame is kept as inApp because it is a native frame. The Java frames from the package are marked as "framework" -> "system (see the data property for evidence of an overwrite):

Not sure if this is really a problem, but it certainly was unexpected.

Please also keep in mind that this PR should be blocked for merging/releasing until UI issues are fixed here: getsentry/sentry#107318. For instance, currently, there is no stable rendering between native and Java frames.

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	311.64 ms	365.73 ms	54.09 ms
Size	0 B	0 B	0 B

Baseline results on branch: main

Startup times

Revision	Plain	With Sentry	Diff
ee747ae	405.43 ms	485.70 ms	80.28 ms
22f4345	313.52 ms	364.96 ms	51.44 ms
d15471f	379.40 ms	470.76 ms	91.36 ms
9fbb112	401.87 ms	515.87 ms	114.00 ms
382d6c1	306.85 ms	368.70 ms	61.85 ms
a5ab36f	316.83 ms	394.54 ms	77.71 ms
96eeafa	361.43 ms	455.07 ms	93.63 ms
dba088c	320.59 ms	361.29 ms	40.70 ms
9054d65	330.94 ms	403.24 ms	72.30 ms
a416a65	333.78 ms	410.37 ms	76.59 ms

App size

Revision	Plain	With Sentry	Diff
ee747ae	1.58 MiB	2.10 MiB	530.95 KiB
22f4345	1.58 MiB	2.29 MiB	719.83 KiB
d15471f	1.58 MiB	2.13 MiB	559.54 KiB
9fbb112	1.58 MiB	2.11 MiB	539.18 KiB
382d6c1	1.58 MiB	2.29 MiB	719.85 KiB
a5ab36f	1.58 MiB	2.12 MiB	555.26 KiB
96eeafa	1.58 MiB	2.19 MiB	620.21 KiB
dba088c	1.58 MiB	2.13 MiB	558.99 KiB
9054d65	1.58 MiB	2.29 MiB	723.38 KiB
a416a65	1.58 MiB	2.12 MiB	555.26 KiB

Previous results on branch: fix/android/id_java_kotlin_frames_tombstone

Startup times

Revision	Plain	With Sentry	Diff
c911bc0	369.24 ms	420.27 ms	51.03 ms
238420b	318.77 ms	364.60 ms	45.83 ms
b9f7b6b	296.53 ms	355.34 ms	58.81 ms
faa47e5	357.79 ms	451.31 ms	93.52 ms

App size

Revision	Plain	With Sentry	Diff
c911bc0	0 B	0 B	0 B
238420b	1.58 MiB	2.29 MiB	720.12 KiB
b9f7b6b	1.58 MiB	2.29 MiB	720.04 KiB
faa47e5	0 B	0 B	0 B

[sentry]

Sentry Build Distribution

App Name	App ID	Version	Configuration	Install Page
SDK Size	io.sentry.tests.size	8.35.0 (1)	release	Install Build

[markushi]

LGTM, nice!, I'll not marked it as approved, as we should get the frontend changes in first.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Tests expect empty string but production code returns null
  • Updated both bare-function Tombstone parser tests to assert null module values, matching production behavior when no module can be extracted.

Or push these changes by commenting:

@cursor push 59609e9828

Preview (59609e9828)

diff --git a/sentry-android-core/src/test/java/io/sentry/android/core/internal/tombstone/TombstoneParserTest.kt b/sentry-android-core/src/test/java/io/sentry/android/core/internal/tombstone/TombstoneParserTest.kt
--- a/sentry-android-core/src/test/java/io/sentry/android/core/internal/tombstone/TombstoneParserTest.kt
+++ b/sentry-android-core/src/test/java/io/sentry/android/core/internal/tombstone/TombstoneParserTest.kt
@@ -13,6 +13,7 @@
 import kotlin.test.Test
 import kotlin.test.assertEquals
 import kotlin.test.assertNotNull
+import kotlin.test.assertNull
 import org.mockito.kotlin.mock
 
 class TombstoneParserTest {
@@ -496,7 +497,7 @@
     val frame = event.threads!![0].stacktrace!!.frames!![0]
     assertEquals("java", frame.platform)
     assertEquals("myMethod", frame.function)
-    assertEquals("", frame.module)
+    assertNull(frame.module)
   }
 
   @Test
@@ -505,7 +506,7 @@
     val frame = event.threads!![0].stacktrace!!.frames!![0]
     assertEquals("java", frame.platform)
     assertEquals("myMethod", frame.function)
-    assertEquals("", frame.module)
+    assertNull(frame.module)
   }
 
   @Test

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}