IssueTracker

Note that in addition to avoiding duplicate events when a transition is already in progress (as explained in the duplicate bug) (which would prevent you from popping the last destination in the first place), note that the back stack documentation does specifically call out handling the return value from navController.popBackStack() to avoid blank screen issues by closing the activity if you really do want to know when you've popped the last destination off the back stack to know you need to finish the activity rather than leave the user on a blank screen.

This is not a duplicate but a regression.

I've sent the fix for the double-click issue to https://github.com/android/socialite/pull/61 follow your docs suggestion. In my case, I just clicked the back button one by one, some of them could return, but some of them went to white, after downgrading navigation-compose to 2.7.7, everything worked well. Please view my attached screen recording.