Status Update
Comments
se...@gmail.com <se...@gmail.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
se...@google.com <se...@google.com>
se...@google.com <se...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
se...@google.com <se...@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-alpha03 Jetpack Compose component used: material3 Android Studio Build: Android Studio Dolphin | 2021.3.1 Patch 1 Kotlin version: 1.7.10
The
Scaffold
contentWindowInsets
does not take into account whether or not the providedWindowInsets
are consumed or not. All the other components (app bar, drawer, etc.) use thewindowInsetsPadding
modifier which only applies the unconsumedWindowInsets
to the respective component.In
Scaffold
, the raw values of thecontentWindowInsets
are used, regardless of whether any part of the insets is already consumed by a parent ofScaffold
, causing the insets to be applied twice. This can be worked around by applying the appropriate insets outside ofScaffold
and settingcontentWindowInsets = WindowInsets(0, 0, 0, 0)
, but it would be helpful if insteadScaffold
only used the unconsumed parts ofcontentWindowInsets
.I'm not entirely sure if this can be solved the same way, but I noticed that the unreleased appears to be doing something similar.
SearchBar
component