Repository navigation
SentryModifier.sentryTag reports zero bounds with Telephoto ZoomableImage on Sentry Android 8.47.0 #5786
Description
Integration
sentry-compose
Build System
Gradle
AGP Version
9.2.1
Proguard
Disabled
Other Error Monitoring Solution
No
Version
8.47
Steps to Reproduce
Clone and open the attached minimal repro project.
Run:
./gradlew :app:testDebugUnitTest
The repro uses:
Sentry Android 8.47.0
Compose UI 1.11.3
Telephoto 0.19.0
Coil 2.7.0
Media3 1.10.1
The composition contains:
a Telephoto ZoomableImage
a sibling Android PlayerView wrapped with SentryModifier.sentryTag
assertIsDisplayed() on that tag.
sentry-compose-bounds-repro.zip
Expected Result
The tagged PlayerView is present with non-zero Compose semantics bounds, and assertIsDisplayed() passes.
Actual Result
The tag is present in the Compose semantics tree, but Compose reports zero-sized bounds for it. Therefore assertIsDisplayed() fails:
Assert failed: The component with TestTag = 'taggedPlayerView' is not displayed!
The same repro passes with Sentry 8.46.0.
A local build of Sentry 8.47.0 with only this change passes the same test:
fun isImportantForBounds(): Boolean = true
Metadata
Metadata
Assignees
Labels
Projects
- Status
Activity
linear-code commentedon Jul 17, 2026
JAVA-657
sentry-pierre commentedon Jul 17, 2026
This is a regression from the #5672 fix for #5662. The
isImportantForBounds() = falsestub avoids theAbstractMethodErroron compose-ui 1.11+, but it also tells Compose that the tagged node doesn't contribute to bounds calculation, which breaksassertIsDisplayed()when siblings likeZoomableImageare present.The proposed fix (
return true) is the right direction:SentryTagModifierNodewraps actual content and should let that content own its bounds. A maintainer can take it from here.github-actions commentedon Jul 22, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #5789, which was included in the 8.50.0 release.