Fixed
Status Update
Comments
an...@seventhbeam.com <an...@seventhbeam.com> #2
Please provide a minimal sample project that reproduces this issue.
il...@google.com <il...@google.com> #3
Sure, I created a minimal sample app for you:
Just click "Next Fragment" multiple times, then press the back button or perform the back gesture multiple times in quick succession.
Note: I tested this on a Pixel 8 with Android 14. Also, I have the predictive back animations enabled in the developer options.
ap...@google.com <ap...@google.com> #4
Just FYI: Still happens on fragment library version 1.7.1
.
il...@google.com <il...@google.com> #5
Still crashing with fragment 1.8.0
. I have updated my example github repo with all latest libraries.
Description
Version used: 1.0.0-beta01
When at start destination the nav controller will consume 2 back presses before popping out of the app. If only 1 navigateUp is called, subsequent navigateTo(...) calls will result in an illegal state exception and crash the app.