fix(compose): add isImportantForBounds() to SentryTagModifierNode for compose-ui 1.11+

CHANGELOG.md

@@ -12,6 +12,7 @@
   - Previously, `SentryGestureListener` always started a UI transaction and only afterwards skipped binding it to the Scope when a manually-bound transaction already existed, leaving the new transaction to be dropped as an idle transaction without children.
 - Fix potential NPE within `Scope.endSession()` ([#5657](https://github.com/getsentry/sentry-java/pull/5657))
 - Fix memory leak in `ReplayIntegration` due to persisting executor not being shut down ([#5627](https://github.com/getsentry/sentry-java/pull/5627))
+- Fix AbstractMethodError when compose-ui 1.11+ is used in combination with `Modifier.sentryTag()` or the Sentry Kotlin compiler plugin ([#5672](https://github.com/getsentry/sentry-java/pull/5672))
 
 ### Performance
 

sentry-compose/src/androidMain/kotlin/io/sentry/compose/SentryModifier.kt

@@ -53,5 +53,15 @@ public object SentryModifier {
     override fun SemanticsPropertyReceiver.applySemantics() {
       this[SentryTag] = tag
     }
+
+    // SemanticsModifierNode.isImportantForBounds() was added as an abstract method in
+    // compose-ui 1.11.  Classes compiled against earlier versions lack this method in
+    // their bytecode, which causes AbstractMethodError when the accessibility tree is
+    // traversed on 1.11+ runtimes.  We can't use the `override` keyword here because
+    // the method doesn't exist in the compile-time dependency (compose-ui 1.6.x), but
+    // the JVM satisfies the abstract-method requirement at runtime via signature
+    // matching.  SentryTagModifierNode only stores a semantic tag and has no visual
+    // effect on layout, so it is not important for bounds.
+    @Suppress("unused") fun isImportantForBounds(): Boolean = false
   }
 }