Possible issue with modifying @State variables within .task?

I ran across a weird issue wherein setting a @State variable from within .task based on an array of values (I tested with UUIDs and random Ints) works properly in SwiftUI but not Compose.

In a nutshell, assume that a view struct has the following variables:

let uuids = [UUID(), UUID(), UUID(), UUID(), UUID()]
@State private var firstUUID:UUID?

This initializes the view with 5 random UUIDs and a firstUUID @State variable set to nil.

Within the view's .task, I attempt to set firstUUID to the first UUID in the array.

.task {
    self.firstUUID	= self.uuids.first
}

This works properly within SwiftUI, but not Compose.

(Real-world context: I want to use UUIDs to model different pieces of model that a user can toggle between in the view...)

I do note, however, that (assuming these views are in tabs) if I click on a different tab and then return the value is set properly in Compose as well. It also seems to work consistently within the second tab. Some sort of timing issue, perhaps?

I tried this using random Ints and saw the same behavior with them, so I don't think it's specific to UUID, per se.

This has been a bit hard to explain, so I've created a test project that I believe demonstrates what I'm seeing. I will attach a screenshot of the output from Compose (left) and SwiftUI (right), respectively.

You'll see that Compose consistently identifies the first UUID in the array within view reconstruction, but comes up with a completely different UUID when it's based on the @State variable.

This might seem a bit esoteric, but I found it while having trouble getting a struct to conform to Identifiable (hence the UUID - I was using one for my struct's id). I imagine others will run across this as well.

Start by running the linked skip-uuidtest project and compare the .task assignment to the @State value during view reconstruction and tab switching. Trace the Compose-side handling of @State and .task to identify why the first UUID differs from the state-backed value. Done means the state assignment behaves consistently with SwiftUI, with regression coverage for UUIDs or random integers.