Status Update
Comments
co...@google.com <co...@google.com>
co...@google.com <co...@google.com>
co...@google.com <co...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
na...@google.com <na...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
co...@google.com <co...@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.
co...@google.com <co...@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
When the app is running in a COMPACT area, both List-Detail and Supporting Pane can show either the main
Composable
(List
orMain
) or the additional one (Detail
,Support
,Extra
). When you are in the secondary one and press back, the current behaviour is to pop out of theScaffold
completely, should we add a back handler that when inCOMPACT
would pop the secondary one back to the main one?As an example, could this be the default behaviour?