I have the same issue with multiple navigate() and I solved it by check current route != next destination. But I don't know how to do it with popBackStack(). Thank you. Very useful.
My first response was "no way, that can't be correct" -- but it sure seems you are right! I am surprised at this find and your fix seems solid (especially liking the extension function). I wonder if this debouncing need is mainly on the emulator since it is so much slower than real HW....
I have something similar I have screen 1 where I can input text and show that on screen . My screen 2 has check boxes both of them has been stored in viewmodel using uiState no livedata or room ... So very weird behaviour. I can input text in screen 1 navigate to screen 2 . Screen 2 has 2 options to go back to screen 1 with TopBar arrow using navigate to screen 1 and the back button on the phone. When I use the TopBar arrow the text disappears from screen one but the back button using popBackstack hold the text on screen1...
This should be included natively in the next version of Compose navigation 😅😅
Great tip, my friend. Thanks for sharing.
Thanks. I also experienced this before. Good point
What a coincidence! My app was doing the exact same thing and I didn't know why, thanks
me too, I couldn't find the reason so I marked it as bug and postponed it, I can't believe the solution is this simple. thanks Steve
Facing this problem could not find a solution!!! Thank you!!!
I have really learnt from this. I had this issue on a slow device. Thank you for sharing
Anytime!
I have the same issue with multiple navigate() and I solved it by check current route != next destination. But I don't know how to do it with popBackStack(). Thank you. Very useful.
Glad to help!
Simple and clear, Thanks!!
Wow, thx. I had that bug too. But i fixed it with delay and button property enabled
My first response was "no way, that can't be correct" -- but it sure seems you are right! I am surprised at this find and your fix seems solid (especially liking the extension function). I wonder if this debouncing need is mainly on the emulator since it is so much slower than real HW....
Probably there's a higher chance on emulator, but still it can happen on a real device as well.
Awesome.
Already faced an issue with it. Thanks.
I have something similar I have screen 1 where I can input text and show that on screen . My screen 2 has check boxes both of them has been stored in viewmodel using uiState no livedata or room ... So very weird behaviour. I can input text in screen 1 navigate to screen 2 . Screen 2 has 2 options to go back to screen 1 with TopBar arrow using navigate to screen 1 and the back button on the phone. When I use the TopBar arrow the text disappears from screen one but the back button using popBackstack hold the text on screen1...
awesome, thanks for the tip!
yes i also facing this issue
So jetpack compose isn't stable yet?
Anything in this world isn't stable. The nature of the things is the caos 🤣🤣
Thank you sir ❤
thank you so much dude
How to show WebView in compose multi platform app for android & iOS
This can happen with anything thats clickable, so the better solution imo is to add multiple click handler thay way user cant press more than once.
Open cv with android Jetpack compose and kotlin is it possible?
great tip!