IssueTracker

Apologies, after re-investigating we've discovered that we can narrow it down to the change from alpha10 to alpha11:

kotlinCompilerExtensionVersion: 1.5.8 +
compose-bom: 2023.10.01 + 
material3:1.2.0-alpha05: works
material3:1.2.0-alpha06: works
material3:1.2.0-alpha07: works
material3:1.2.0-alpha08: works
material3:1.2.0-alpha09: works
material3:1.2.0-alpha10: works
material3:1.2.0-alpha11: broken
material3:1.2.0-alpha12: broken
material3:1.2.0-beta01: broken
material3:1.2.0-rc01: broken

kotlinCompilerExtensionVersion: 1.5.8 +
compose-bom: 2024.01.00 +
material3:1.2.0-alpha10: works
material3:1.2.0-alpha11: broken

we have no explicit dependency on compose-ui, just these:

library("androidX.compose.bom", "androidx.compose", "compose-bom").version("2024.01.00")
library("androidX.compose.material3", "androidx.compose.material3", "material3").version("1.2.0-alpha10")
library("androidX.compose.uiToolingPreview", "androidx.compose.ui", "ui-tooling-preview").withoutVersion()
library("androidX.compose.debugUiTooling", "androidx.compose.ui", "ui-tooling").withoutVersion()

Attached is a screenshot of the Appium inspector for this specific screen, after expanding the DropDownMenu on alpha10. The middle column shows an XML representation of the hierarchy of the components on the screen. Note that these talk about Views, but the entire UI is built in Compose.

In tests, we refer to specific elements on the screen by looking up either:

• the xpath: /hierarchy/android.view.ViewGroup/android.view.View/android.view.View/android.view.View/android.widget.ScrollView/android.view.View[1]
• the resource-id that we set on specific elements, like HD in this example.

For each of the 4 scenarios, I've added the XML from the center column. Note that for alpha11 both XMLs are the same, meaning that the elements in the DropDownMenu seem to be not visible to the Appium inspector. Also note that in the expanded state, only the DropDownMenu elements are shown. Not the elements on the screen underneath.

Lastly, I attached 2 screenshots of the Android Studio Layout inspector for the collapsed and expanded state. These were identical between alpha10 and alpha11. I see here that the FrameLayout and the ExposedDropDownMenu are at the same level, and in the alpha10 case, the Appium inspector only shows one of these as XML. Could it then be that there was a change in the ordering of these two, making it so that the first one is now always the background content? (if the Appium inspector always takes the first one, that would explain why it no longer presents/finds the DropDownMenu content)

I noticed that a new bom was released today, so I tried it out:

kotlinCompilerExtensionVersion: 1.5.8 +
compose-bom: 2024.02.00 +
material3:1.2.0-alpha10: broken
material3:1.2.0-rc01: broken

kotlinCompilerExtensionVersion: 1.5.9 +
compose-bom: 2024.02.00 +
material3:1.2.0-alpha10: broken

It seems that the change in compose-ui affected the behavior, unfortunately, it now also shows the 'broken' behavior on the 1.2.0-alpha10 version, which worked before.

Extra information:

• We use UiAutomator2 for our appium configuration, so its also feasible that uiAutomator2 needs to be fixed.

Hi, we have the same issue on Appium not seeing exposed menu popup window contents but we are using Material2 version of the exposed APIs:

import androidx.compose.material.ExposedDropdownMenuBox

Additionally we noticed the regression affected also the window focus. Before it broke, you could open the exposed popup window and it would be taking key events in and you could navigate thorugh the DropdownMenuItems but after it broke, the focus stays on the screen beneath the popup window.

I hope this helps to narrow down the issue root.

Given this is the broken popup window focus, can we give it a higher priority, please?

Commenter #6, could you please share what version of Material 2 / compose-bom you are using?

| Re #8

We bumped our Compose dependency BOM from 2023.10.01 to 2024.02.00 and then got hit with this regression.

    implementation(platform("androidx.compose:compose-bom:${Versions.COMPOSE_BOM}"))
    api("androidx.compose.ui:ui")
    api("androidx.compose.foundation:foundation")
    api("androidx.compose.material:material")
    api("androidx.compose.ui:ui-tooling-preview")
    api("androidx.compose.material:material-icons-extended")
    api("androidx.compose.material3:material3")
    api("androidx.compose.runtime:runtime-livedata")

This is only needed for a 1.2.0 cherrypick.

M compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/internal/ExposedDropdownMenuPopup.android.kt

Commenter #10

Will this be fixed also for Material2 i.e. androidx.compose.material:material:1.6.2 ?

comment#11: Yes this will be fixed in Material 2 as well.

What Compose [BOM] version can we expect the fix for M2 and M3 in?

comment#13: Barring anything unexpected, we are targeting the fixes for androidx.compose.material:material:1.6.3 and androidx.compose.material3:material3:1.2.1. A new BOM should be available when this happens.

Thank you! That sounds awesome.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.material:material:1.6.3
• androidx.compose.material:material-android:1.6.3
• androidx.compose.material:material-desktop:1.6.3
• androidx.compose.material:material:1.7.0-alpha04
• androidx.compose.material:material-android:1.7.0-alpha04
• androidx.compose.material:material-desktop:1.7.0-alpha04
• androidx.compose.material3:material3:1.2.1
• androidx.compose.material3:material3-android:1.2.1
• androidx.compose.material3:material3-desktop:1.2.1
• androidx.compose.material3:material3:1.3.0-alpha02
• androidx.compose.material3:material3-android:1.3.0-alpha02
• androidx.compose.material3:material3-desktop:1.3.0-alpha02

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.material3:material3:1.3.0-alpha03
• androidx.compose.material3:material3-android:1.3.0-alpha03
• androidx.compose.material3:material3-desktop:1.3.0-alpha03