createComposeRule() with Target SDK 35 causes ActionBar overlapping in default theme [383368165]

Fixed

Bug

Status Update

No update yet.

Description

ta...@gmail.com

created issue #1

Dec 11, 2024 01:54AM

Jetpack Compose version:

BOM 2024.09.00

Jetpack Compose component(s) used:

Compose Testing (createComposeRule)

Android Studio Build:

Android Studio Meerkat | 2024.3.1 Canary 3 Build #AI-243.21565.193.2431.12691553, built on November 21, 2024 Runtime version: 21.0.5+-12651406-b631.16 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Toolkit: sun.lwawt.macosx.LWCToolkit macOS 14.4.1

Steps to Reproduce or Code Sample to Reproduce:

Set the Target SDK to 35.
Use createComposeRule() in a test file without specifying a custom theme.
Run the following code in an instrumented test(androidTest):

@RunWith(AndroidJUnit4::class)
class ExampleInstrumentedTest {
    @get:Rule
    val composeTestRule = createComposeRule()

    @Test
    fun useAppContext() {
        composeTestRule.setContent {
            Text("Hello\n\n\n\n\n\n\n\n\n\n World")
        }

        Thread.sleep(10000) // Observe the UI
    }
}

Expected Behavior:
The default theme should prevent the ActionBar from overlapping the Compose content, as most users use themes without ActionBars in Compose-based projects. In fact, newly created Android projects use android:Theme.Material.Light.NoActionBar by default, which naturally avoids this issue. Updating the default testing environment to set windowActionBar=false would better align with typical use cases and expected behaviors.

Actual Behavior:
The ActionBar is displayed and overlaps the Compose content. This leads to confusion, especially for beginners or developers trying to test simple layouts, as their content may not appear as expected.

Relevant Pull Request:
https://github.com/android/nowinandroid/pull/1719

Wed Dec 11 2024 10:45:04 GMT+0900 (Japan Standard Time).png

Restricted

788 KB

View

Download

Comments

je...@google.com <je...@google.com> #2Dec 16, 2024 06:03PM

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?

ta...@gmail.com <ta...@gmail.com> #3Dec 17, 2024 12:31AM

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

je...@google.com <je...@google.com> #4Dec 17, 2024 02:34PM

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.

an...@google.com <an...@google.com> Dec 17, 2024 07:33PM

Assigned to je...@google.com.

ta...@gmail.com <ta...@gmail.com> #5Dec 17, 2024 11:51PM

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.

ap...@google.com <ap...@google.com> #6Dec 20, 2024 05:40PM

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)

je...@google.com <je...@google.com> Jan 6, 2025 06:56PM

Marked as fixed.

pr...@google.com <pr...@google.com> #7Jan 15, 2025 06:31PM

FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model. https://developers.google.com/ml-kit/release-notes#august_11_2021

Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!

IssueTracker