IssueTracker

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:

1. Set the Target SDK to 35.
2. Use createComposeRule() in a test file without specifying a custom theme.
3. 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.

Related links

Reproduced Repository:
https://github.com/takahirom/createComposeRule-ActionBar-Overrapping-issue/blob/main/module/src/androidTest/java/com/github/takahirom/module/ExampleInstrumentedTest.kt

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