Using CollapsingToolbarLayout with navigation [110887183]

Fixed

Bug

Status Update

No update yet.

Description

ju...@gmail.com

created issue #1

Jun 28, 2018 03:07PM

Component used: android.arch.navigation:navigation-ui
Version used: 1.0.0-alpha02
Devices/Android versions reproduced on: all devices (e.g. Pixel 2, Android 8.1.0, API27)

I'm not quite sure this is a bug but I'm having trouble using Navigation UI component with both standard Toolbar and CollapsingToolbarLayout. Is there a plan to include some kind of support for this?
Because switching between items in the bottom navigation that I have and having some of the screens using standard toolbar and some of them CollapsingToolbarLayout it is really difficult to combine.

I went for a solution of having a standard Toolbar in the Activity and CollapsingToolbarLayout in the fragment and when I display this fragment, I hide the toolbar in the Activity. This however creates ugly flickering and moving of the content, which looks bad and also it happens so that Bottom navigation bar gets pushed down too much until I invalidate it.

Comments

il...@google.com <il...@google.com> #2Jun 28, 2018 04:35PM

Assigned to il...@google.com.

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ju...@gmail.com <ju...@gmail.com> #3Jun 28, 2018 06:36PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

screencapture-1530209526017.mp4

734 KB

Download

il...@google.com <il...@google.com> #4Jun 28, 2018 07:35PM

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.

ju...@gmail.com <ju...@gmail.com> #5Jun 29, 2018 09:46AM

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.

il...@google.com <il...@google.com> Jul 9, 2018 06:23PM

Accepted by il...@google.com.

il...@google.com <il...@google.com> #6Jul 10, 2018 12:03AM

Marked as fixed.

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)

Issue 110887183