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)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 84651]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides.
See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 746686]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides. See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 920908]
[ID: 966373]
[ID: 966375]
[ID: 966382]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Description
The conditions to trigger this bug seem to be very specific, so bear with me:
movableContentOf
that calls another composable lambda,MutableState
,LazyColumn
orLazyVerticalGrid
) to inside it,MutableState
holding the inner lambda is assigned a new lambda from inside the lazy layout immediately after the content is movedHowever,
Simple repro
This is the smallest repro case I could come up with. To reproduce the bug, check the box and then uncheck it. The crash should happen as soon as you uncheck it.
Code:
Exception (full trace attached as
simple-repro-stacktrace.txt
):Complex repro
However, in other cases the exception is very different. If you check out this github repo at the , run the
movable-in-lazy-repro
branchgalaxyapp
, tap on a grid item and then navigate back, you should get a crash after the animation with this exception (stack trace also attached asgalaxyapp-stacktrace.txt
):