Fixed
Status Update
Comments
co...@google.com <co...@google.com>
ap...@google.com <ap...@google.com> #2
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?
le...@google.com <le...@google.com>
na...@google.com <na...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com <ap...@google.com> #4
-
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
Jetpack Compose component used: material3-adaptive-navigation-suite
Android Studio Build: Android Studio Iguana | 2023.2.1 Canary 14
Kotlin version:
Steps to Reproduce or Code Sample to Reproduce:
1. Open project (or create new Navigation Suite project and add a simple Composable as part of the NavigationSuiteScaffold content)
2. Run the project
Preview shows Navigation Suite working fine, but when run on device, the BottomNavigationBar appears in the middle of the screen (and NavRail as well), and the content Composable is not shown. I could replicate this error on Pixel Fold and Pixel 7 Pro, both running Android 14.
Invalidate and restart or rebuild the app didn't fix the issue, but removing the Size modifiers from the root Surface fixed it.