App Freezes and Crashes when Backing out of Settings with 3-Button Navigation

[ZmaZes]

App Version: 4.6.0
Android: 14
Model: Samsung ZFlip 5

When opening settings in the app, and trying to close it using the back button on the navigation bar, the app freezes (although you can feel haptic feedback from the tempo wheel if you slide your finger over where it would be). Pressing back again quits the app, presumably because it thinks it's.already on the main menu.
The issue does not occur when using gesture navigation or when clicking the back button on the top left of the screen. I assume this is some glitch that came with the addition of predictive back animation support.

[patzly]

Thanks for the report! A workaround would be to switch to gesture navigation, but I couldn't find a real fix yet. The problem is caused by the navigation library from Google, so I have to open an issue for that I think.

[ZmaZes]

I think I'll just use the back button in the upper left. My navigation setup is a bit in depth so switching to plain gesture navigation isn't quite an option for me. (The swipe for back button gesture I use (one hand operation) has the same effect as just pressing the button on the navbar, it doesn't support the predictive back animation.)
I've seen other apps that use predictive back animations that don't have the issue, so I'm sure it's possible somehow (Image Toolbox by ProgiX works just fine for example.)

[patzly]

The app Image Toolbox is written in Compose which uses another variant of the navigation component, so the bug is in another version of the library which is used by Tack.

[ZmaZes]

Not sure if this helps bug test at all or if you already figured this out youself, but it seems like the bug doesn't actually make the app freeze, rather it takes you back to the home screen, but the settings screen is still visible. So you can interact with all of the elements on the home screen even though you can't see them.
I also noticed that when the bug happens, you can go to recents, and then re-open the app from there, and the problem is gone, at least for the time.