Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
This is a great idea as it solves one major pain experienced by my developer using Compose.
Another solution idea would be to use "onAppear" modifier to allow each composable have an individual event handler.
For example:
```
Column(
modifier = Modifier
.fillMaxSize()
.onAppear {
viewModel.loadItems()
}
) {
...
}
```
Another solution idea would be to use "onAppear" modifier to allow each composable have an individual event handler.
For example:
```
Column(
modifier = Modifier
.fillMaxSize()
.onAppear {
viewModel.loadItems()
}
) {
...
}
```
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
As simetrias podem posicionar-se alternadamente face ao número de módulos disponíveis para o efeito de cada fase
Description
I have created a Sample app to demonstrate the problem, and setted a delay of 1 sec. To see the crash just click the button when it will appear. The funny thing is that if you go to other tab and come back - The navigation will work.
The exception I'm getting is:
`java.lang.IllegalArgumentException: navigation destination com.example.myapplication:id/action_homeFragment_to_second2 is unknown to this NavController`