Status Update
Comments
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
ab...@google.com <ab...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
dp...@phunware.com <dp...@phunware.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ma...@google.com <ma...@google.com>
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.
pr...@google.com <pr...@google.com> #5
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
Jetpack Compose version: 1.1.0-alpha07 Jetpack Compose component used: Material3
As described in the Material3 Guidelines, shadow elevation should be used to separate components from patterned or busy backgrounds.
The SearchBar component already supports tonal elevation, but if we need to use it on a busy background (like over a map view, for example), that's not enough to protect the component and indicate separation.
The
Surface
component already supports ashadowElevation
parameter and some other components that useSurface
also already have that parameter that they pass down to the underlyingSurface
, like theListItem
component.Can we please do the same for the SearchBar component? Simply adding a
shadowElevation
parameter and passing it to theshadowElevation
of theSurface
is enough to fix this. I copied the SearchBar component and tested the change and it worked fine.Thanks.