IssueTracker

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

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

This should be fixed by aosp/1959647

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

I wonder if this is related to the issue described in this blog post.

This still seems to be an issue on 1.2.0-beta03

A workaround that seems to be working for us is to have a delay before requesting focus.

LaunchedEffect(focusRequester) {
    delay(100)
    focusRequester.requestFocus()
}

Confirmed that the text field is actually getting focus from the effect, so this is definitely an IME issue and not a focus one.

Is there a workaround for this? The issue happens for components that are a part of androidx.compose.ui.window.Popup as well.

I get the following error when a BasicTextField component within a Popup requests focus:

Ignoring showSoftInput() as view=androidx.compose.ui.platform.AndroidComposeView{50b009a VFED..... .F....ID 0,0-1079,2218} is not served.

And the keyboard doesn't show.

When I try to force the keyboard to show using

val imm: InputMethodManager =
    LocalContext.current.getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager
imm.toggleSoftInput(InputMethodManager.SHOW_FORCED, 0)

I see that the keyboard renders behind the Popup component (In my case the contents of the Popup take up a good portion of the screen).

Is there no way to control the Z axis of the contents of my Popup to show behind the system keyboard?

Or is it just not recommended to have a text input field inside a Popup at all?

Also experiencing the same issue (1.4.0-alpha04) as #8 regarding soft keyboard showing behind dialog and so keys cannot be pressed. Any workaround?

EDIT: note, I'm using com.google.android.material.dialog.MaterialAlertDialogBuilder and setting the content view with a ComposeView

Also still experiencing this. On compose 1.3.1. Dumb workaround is to use a delay(100).

A more robust workaround that worked for me was waiting for window focus.

val windowInfo = LocalWindowInfo.current

LaunchedEffect(windowInfo) {
    snapshotFlow { windowInfo.isWindowFocused }.collect { isWindowFocused ->
        if (isWindowFocused) {
            focusRequester.requestFocus()
        }
    }
}

Any update on this? Experiencing this in M3 and Compose 1.6.

Causes our UI tests to fail about 20% of the time since our UI tests are written with the keyboard open and thus when it's not causes scrolling and assertion issues.

This should be fixed in 1.7.

Can you link to the commit where this was fixed? I'm interested in the implementation that fixes this. Also, is the fix available in 1.7.0-beta02 release?