IssueTracker

Information redacted by Android Beta Feedback.

I tried adding a hook in the onFocusChanged event of the textField Modifiers to scroll up, but doesn't seem to work as the view has yet to be resized, so it ends up as a no op when selecting a field at the end of the list. Are there any workarounds to this? As this is a pretty severe show stopper on my end and I have to resort to a recycler view instead...

Wow I actually came across this hilariously weird bug as well. For whatever reason a re-composition is triggered when you click the textfield, making it loose focus.

I noticed that the problem only occurs when the keyboard is fully overlapping the TextField. Slightly altering your example and scrolling fully to the bottom """fixes""" the issue.

LazyColumn(Modifier.navigationBarsWithImePadding()) {
    repeat(5) {
        item {
            Surface(Modifier.size(200.dp), color = Color.Blue) {

            }
            Spacer(Modifier.height(16.dp))
        }
    }
    item {
        TextField(value = "", onValueChange = { })
        Spacer(Modifier.height(400.dp))
    }
}

This led me to believe that window resizing is causing these re-compositions(?).

So I tried using android:windowSoftInputMode="adjustPan" which prevents this and as expected this also """fixes""" the issue (not really).

Also, why does this only have P4 priority? Doesn't it make any basic editable form in a lazy column impossible to develop? However, it does sound like a few other keyboard issues mentioned here, so perhaps it's being addressed elsewhere.

P4 means not triaged yet.

CC'd others, this is again in the intersection of multiple components: lazy column, focus, window resize, maybe also textfield.

#6

This led me to believe that window resizing is causing these re-compositions(?).

That's because navigationBarsWithImePadding() will change the state when insets changed.

That's because when textfield losing focus it's automatically triggering notifyTextInputServiceOnFocusChange Thus under the hood will hide keyboard by TextFieldDelegate.onBlur(session, state.processor, onValueChange) Seems that right now we don't have any option to prevent autohiding keyboard on focus lose. Found this, because I have screen with many inputfields, and I noticed that keybaord reinvalidating on cursor change from textfeild to textfield, and thats became a problem if textfields has different input type (text/number) In this case keybaord has different heigh and the content starts jumping if pushed by ime-insets😢

Bulk edit: This bug is currently marked as blocking Compose 1.0. Once rc01 is cut, all changes will need to go through our cherry-pick process.

If you intend to fix it in Compose 1.0, no action is needed except prioritizing finishing this work.

Otherwise, please remove this bug from the appropriate 1.0 hotlist (likely Jetpack Compose 1.0 (May 2021)) and add it to Post-1.0 (or not-yet-prioritized).

Thanks!

I took a look at this today and couldn't reproduce the automatic keyboard hiding with the tip of tree build. I think this is related to the navigationBarsWithImePadding modifier. Will re-visit this later. For now, I attached a gif of what I see:

Huh I've retried it with beta-08 and I confirm I was not able to reproduce the error. See the attached video where I try at different positions in the list, the window even resizes correctly!

Thanks for confirming! I'm going to mark this as fixed.

I found a weird issue about LazyColumn

https://github.com/google/accompanist/blob/main/sample/src/main/java/com/google/accompanist/sample/insets/ImeAnimationSample.kt#L121

Under adjustResize mode, when setting reverseLayout = true, the content will shift up with keyboard showing up, just like adjustPan effect, if I don't reverse the layout, the content won't shift up and will covered by keyboard, makes the TextField out of canvas, so keyboard dismissed.

Is there any chance make same shift effect without reversing layout?

I was able to reproduce this. This happens because the focus item is disposed when it is scrolled out of view, which causes it to lose focus. I filed b/195049010 to track this issue.

Assigning this to the text team for now, b/195049010 tracks the underlying issue in LazyList that needs to be fixed.

I am also experienced this bug in 1.2.0-beta02 and before. I have a TextField in a scrollable LazyColumn and when I click into the field, the keyboard opens up and closes immediately.

Still happens in 1.2.0-beta02

still happening in 1.2.0-rc02. Any update on this issue? This is a major blocker for us.

Hi there. This issue is of high importance to us and we are actively working on fixing it. However, it is caused by an intricate combination of issues and a fix is not trivial. We've most recently been focusing on https://issuetracker.google.com/issues/195049010 and https://issuetracker.google.com/issues/259274257 that block this specific bug. Cheers;

Hi there, should be available in the next Compose foundation release, by mid January. Cheers.

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

• androidx.compose.foundation:foundation:1.4.0-alpha04

FYI this is still broke using LazyVerticalGrid with compose 1.4.0-alpha04

@Composable
fun TestScreen() {
    val values = remember { mutableStateMapOf(*Array(20) { it to "" }) }
    LazyVerticalGrid(columns = GridCells.Fixed(1)) {
        itemsIndexed(values.keys.toList()) { i: Int, _: Int ->
            TextField(
                value = values[i] ?: "",
                onValueChange = { newValue ->
                    values[i] = newValue
                },
                label = {
                    Text("Field number $i")
                }
            )
        }
    }
}

Confirmed this is an issue specific to LazyVerticalGrid, filed b/265352893.

When I use "androidx.compose.foundation:foundation:1.4.0-alpha04", LiveData Transformations no longer works error: "Unresolved reference: Transformations" livedata version: "androidx.lifecycle:lifecycle-livedata-ktx:2.5.1" any suggestions to fix this issue?