Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
Jetpack Compose version: 1.7.8
Jetpack Compose component(s) used:
Modifier.graphicsLayer
,Modifier.layout
,derivedStateOf
Android Studio Build: #AI-242.23726.103.2422.12816248, built on December 18, 2024
Kotlin version: 2.1.0
the
Modifier.graphicsLayer
from one Composable functiton are unexpectedly applied to a subsequent Composable function under specific conditions, causing unintended visual results.Steps to Reproduce or Code Sample to Reproduce:
Expected Behavior:
Actual Behavior:
This appears to be related to how the Compose rendering pipeline handles the graphicsLayer state between Composable recompositions. The graphicsLayer settings seem to persist between Composables rather than being properly isolated.
Here's a workaround I found that resolves the issue: