Status Update
No update yet.
Comments
se...@google.com
sg...@google.com
ap...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
sa...@gmail.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
sg...@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.
bo...@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.
sg...@google.com
On the contrary, there was no separate process before, when crashes started.
In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)
backtrace:
#00 pc 000000000003c7c0 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003b960 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003bb48 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003bafc /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000036c98 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000032714 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000031cac /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000057438 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)
Description
Jetpack Compose component used: TopAppBar
The Material3 spec says the TopAppBar height must always be 64dp and this is enforced in the library, but sometimes it's just too big, and one good example of this is in landscape mode where vertical space is at at a premium.
Factoring in the system bars, 64dp is around 20% of the available vertical space in landscape mode on typical phones. There's even less space if an app uses a bottom navigation bar. The Play Store app is a good example that even first party apps are affected by this. In landscape mode, there is only space for a single row of app icons when browsing apps on the Play Store.
There is currently no standard pattern to add anything more to the TopAppBar in Landscape mode than a navigation icon, title and action icon buttons which are there in portrait. This means that the extra horizontal space in landscape mode ends up unused.
It would be great if we could have some more control over the TopAppBar height, to make it smaller than 64.dp. Due to the minimum touch target size of 48dp, I've used a 48dp height TopAppBar in my app which I'm quite happy with.
In portrait mode too, having a 56dp height TopAppBar allows for a slightly more compact layout on devices with smaller screens.
Thanks!