Status Update
No update yet.
Comments
lp...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ad...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@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.
ha...@gmail.com
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
Using the AlertDialog API as shown in the sample code here:https://cs.android.com/androidx/platform/tools/dokka-devsite-plugin/+/master:testData/compose/samples/material/samples/AlertDialogSample.kt;l=36 yields a dialog that extends all the way to the device screen edges as shown in the attached screenshot.
AlertDialogs should leave space near the edges as
android.app.AlertDialogdoes.We should address this prior to 1.0 if we can; as-is it's seemingly mandatory to add a
Modifier.padding(24.dp)to AlertDialog usages to avoid the edges of the screen.Other adaptive behavior for larger screens is out of scope for this change.