Fixed
Status Update
No update yet.
Comments
il...@google.com
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
jb...@google.com
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
il...@google.com
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
Description
Version used: 2.1.0-alpha03
Devices/Android versions reproduced on:
If you repeat Navigate with URI, the back key does not work.
I'll attach the sample project. Please check below how to reproduction.
1. Tap `MOVE TO A`
2. Tap `MOVE TO B`
3. Tap `MOVE TO D` (Navigate with URI to another nav graph)
4. Press back key.
5. Repeat step 3 and step 4 2 times
6. We can't back to Fragment A.
I think mBackStack is not correct in NavGraphNavigator and NavController.
When step3, NavGraphNavigator#navigate is not called, but NavGraph is added to NavController.mBackStack.
Thanks.