A modern programming language that makes developers happier.

kotlinlang

Screen_recording_20241002_103225.mp4

I’m experiencing unexpected behavior with navigation in my app that I was able to reproduce in the _*NowInAndroid*_ app and I’m wondering if this behavior is in-fact expected and a non-issue.
Currently, if I navigate to a screen that’s is a “top-level” (in bottom nav. bar) from another “top-level” screen, the app will correctly navigate to but if I attempt to navigate to that previous “top-level” screen by pressing the corresponding bottom nav. bar item. The app does not navigate. Pressing navigating “up” by pressing the back button will clear the current “top-level” screen from the back stack and selecting the destination from the bottom nav. bar works again.
This to me, appears to be a bug, and not what I would expect as a new user my app, but since I also see this in _*NowInAndroid*_ I don’t feel as confident.
Here is a demo of the behavior in _*NowInAndroid:*_

Screen_recording_20241002_104553.mp4

Here is a another demo where I get the behavior to occur for two different “top-level” destinations (*For You*, and *Saved*)

To me, this definitely looks like a bug… I would make an issue with Google!