Android instrumented tests get DummyViewConfiguration instead of AndroidViewConfiguration [347740888]

Fixed

Bug

Status Update

No update yet.

Description

je...@google.com

created issue #1

Jun 17, 2024 07:40PM

The following androidInstrumentedTest fails, informing me that it finds a LayoutNode$Companion$DummyViewConfiguration

@Test
fun test() {
    rule.setContent { Box(Modifier.size(10.dp)) }
    assertThat(rule.onRoot().fetchSemanticsNode().layoutInfo.viewConfiguration)
        .isInstanceOf(AndroidViewConfiguration::class.java)
}

Tests should get the same ViewConfiguration as Compose runtime.

Edit: added a better test in #comment2

Comments

je...@google.com <je...@google.com> #2Jun 18, 2024 01:42PM

Over to Ralston to take a look. I imagine with the new relocation logic it should be fixed?

ViewConfigurationTest.patch

2.2 KB

View

Download

mn...@google.com <mn...@google.com> Jun 18, 2024 04:07PM

Reassigned to mo...@google.com.

mo...@google.com <mo...@google.com> #3Jun 25, 2024 07:44PM

What is happening here is that the TextField does not know that it is in a scrollable container, and since the keyboard is going to hide the currently focused text, the text field calls View.requestRectangleOnScreen which causes the entire app to pan up, and that clips the top bar.

The Relocation APIs are experimental right now. It is not used in TextField as we are past the alpha stage and can only use stable APIs in TextField. So this bug can only be fixed post 1.0

ap...@google.com <ap...@google.com> #4Jun 27, 2024 01:10PM

Marked as fixed.

This should be fixed by aosp/1959647

I verified that this sample code now works when soft input mode is AdjustResize.

Issue 347740888

Description

Issue summary

Comments

je...@google.com <je...@google.com> #2Jun 18, 2024 01:42PM

mn...@google.com <mn...@google.com> Jun 18, 2024 04:07PM

mo...@google.com <mo...@google.com> #3Jun 25, 2024 07:44PM

ap...@google.com <ap...@google.com> #4Jun 27, 2024 01:10PM

Add comment

Issue metadata