After updating to Alpha07:

java.lang.IllegalArgumentException: Invalid slot table detected

🤦‍♂️

Already working on that

have you updated to v1.0.0-alpha02 of

navigation-compose

?

yes

yeah, just went back to alpha01 of navigation and it's different crash all right

NoSuchFieldError: No field Companion of type Landroidx/compose/runtime/SlotTable$Companion; in class Landroidx/compose/runtime/SlotTable; or its superclasses (declaration of 'androidx.compose.runtime.SlotTable' appears in

You can't mix and match versions - Nav alpha02 builds against Compose alpha07

yeah, in my case I had forgotten to update to alpha02 when I got that......had remembered that there was some kind of "slot" error so had thought maybe it was same issue that @jaqxues was having

Probly using the deprecated Text from the foundation package

that was it, thanks....just updated that repo (PeopleInSpace) with that change and those version updates

I can't easily reproduce the issue, it is pretty complex The issue happens after toggling this Switch. If I comment out both Icons, it does not crash.

Can you put this in a bug? Code to repro starting from empty template or something would be great

The architecture is pretty complex, as follows: ViewModel with LiveData<List<Elements>> These elements have a state, so for each Element I have an individual livedata for its state Now when the switch changes, the individual state updates and since that is observed as state, it should fire off recomposition. The issue itself seems to come from the IconButton, more specifically the rememberInteractionState(). That is probably the slot element that dpesnt have a parent anchor (or whatever the reason is). I have not figured out why yet, and as stated above the issue is not really very easily reproducible. I'll try to put a reproduction sample together, but I already tried just the composables and I think the LiveData architecture might be a factor in this, or even the exact composable hierarchy. I just haven't been able to get it to fail like in the actual Project

gotcha. and the project isn’t open source, correct?

I use AnimatedVisibility in my Code, seems like that is the issue. Removing that part and having the view "expanded" (with full content at all time), it works fine

do you have an example of the before/after that produces the error? This is very likely an underlying bug in the new slot table implementation that animated visibility just seems to be triggering

What do you mean before/after? I just replaced

AnimatedVisibility(isExpanded, content=content)

with

if (isExpanded) content()

that is what i mean, just a more complete example to repro if possible?

As I said i could not reproduce it, even by copying the entire screen and exchanging my data objects with just strings etc

Also getting

Invalid slot table detected

as well but with a different complex implementation, will try to see if we can narrow down

@Vincent tiensi wouldnt recommend trying to narrow it down. They just need to be able to reproduce your issue. And since i know how this bug is very complex, i suppose its easiest to share the project with them if you can

Ah yeah that’s what I meant, by making the code bit smaller so that they can debug more closely, we inadvertently fixed it by changing this

val state = unwrappedState.value ?: return@Box

to this

when (val state = unwrappedState.value){
//continue

interesting. the early return in the RHS of the nullary expression is probably the culprit here. Is there a bigger view of this function that you can provide me?

I do not know if there were updates to it, but alpha08 fixed it.