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

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

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

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

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

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

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

deleted

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

Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.

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

Hello, I am trying to implement the same thing - it seems like there's no way for current password managers like 1Password or Bitwarden, to automatically pick up the fields. Is there a possible solution?

IssueTracker