Fixed
Status Update
No update yet.
Comments
km...@keepersecurity.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?
si...@google.com
si...@google.com
ma...@google.com
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
pr...@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
Jetpack Compose component(s) used: NavigationBarItem
Android Studio Build: 2022.1.1 Canary 9
Kotlin version: 1.7.0
Steps to Reproduce or Code Sample to Reproduce:
1. Use NavigationBar with NavigationBarItem
2. Use overridden colors with NavigationBarItem with a transparent/translucent indicatorColor
3. The NavigationBarItem composable overrides the alpha channel of the color such that only solid indicator colors can be used.
It would be really helpful if we could use a transparent/translucent indicatorColor. We'd like to hide the pill color entirely to match approved design. The pill was heavily opposed and so we can't have it visible. But we can't hide the pill without completely copying the NavigationBarItem composable and A LOT of supported code, just to remove the `.copy(alpha = animationProgress) part of the indicator composable.
Can this Composable be modified to either (1) support transparent/translucent indicatorColor values and/or (2) completely hide the indicator composable (pill shape on the selected item).
Stack trace (if applicable):
```
<add stack trace here>
```