Trying to change a state in the background, sometimes I get the following error "Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied".

// fetch all the items when the inventory change
    launchInComposition(inventory) {
        val currentInventory = inventory.value
        withContext(<http://Dispatchers.IO|Dispatchers.IO>) {
            // fetchAllItems() update the state
            currentInventory.fetchAllItems()
        }
    }

cc @Chuck Jazdzewski [G]

Can you file a bug with a repo case?

@manueldidonna Did you file a bug for this? I’ve got another snapshot bug happening with subcompositions, I don’t think it’s related but i’d like to follow this bug as well.

The above code does not give me enough context to determine why this is happening. The reason this would happen is if

inventory

is accessed before the snapshot it was created in is applied. Maybe @Adam Powell can give more context on what snapshot

launchInComposition

should be running in.

it launches undispatched when we run composition lifecycle observers and runs as a child job of the recomposer's compose and apply loop

I can file a bug If it's still needed @Chuck Jazdzewski [G]

That would help as I need more context to determine what is going wrong here.

https://issuetracker.google.com/u/1/issues/166486000 I hope this report is useful enough

Thanks for the report! I replied in the report with a work-around you can use now. We are discussing how the above should work. Your code should work as written. However, now,

withContext(<http://Dispachers.IO|Dispachers.IO>)

does not ensure it runs after the composition snapshot has been applied which could cause this code to fail. The work-around prevents the

withContext

from executing until after composition's snapshot has applied.