Status Update
Comments
jb...@google.com <jb...@google.com>
il...@google.com <il...@google.com> #2
I'm also seeing this crash, its the largest crash in my app by far. Thanks for reporting this
be...@citymapper.com <be...@citymapper.com> #3
I am on Samsung Galaxy Z Fold 5. Android 14. Very easy to reproduce when I unfold the phone and switch between navigation rail items very quickly. When the phone is folded the error cannot be reproduced (at least for me).
il...@google.com <il...@google.com> #4
Updated stats on my side :
98% affected (unique) users are Samsung devices (2% motorola) - from 100 bug occurences over 10k+ users
100% are on Android 14
98% affected (unique) users are Samsung devices (2% motorola) - from 100 bug occurences over 10k+ users
100% are on Android 14
ap...@google.com <ap...@google.com> #5
In our case, to reproduce the crash, we press simultaneously the Action Bar back arrow (navController::navigateUp) AND the hardware back button.
This way we get the stacktrace:
java.lang.ArrayIndexOutOfBoundsException: length=10; index=-1
at java.util.ArrayList.get(ArrayList.java:439)
at androidx.navigation.compose.NavHostKt$NavHost$25$1.invokeSuspend(NavHost.kt:518)
- navigation-compose 2.8.3
- activity-compose 1.9.3
- Android 12 (API 31)
Description
In Navigation 2.3.1 and below, setting enter/exit transitions to
0
in NavOptions when navigating to an Activity destination would suppress the activity transitionWithhttps://android-review.googlesource.com/c/platform/frameworks/support/+/1489583/ in 2.3.2 the Navigator attempts to get the resource type name for enter/exit animations. If
0
is passed, this crashes with aResourceNotFoundException