IssueTracker

Sure, I'll test it again and be back with the results tomorrow.

This still happens in Compose 1.3.0-alpha02, see duplicated issues for new steps and code (https://issuetracker.google.com/issues/240449669, https://issuetracker.google.com/issues/240455030)

This seems like a pretty big oversight as it makes validation of the text fields (such as preventing user from entering more than N characters) very bad experience for the user. And no responses since 2020...

This is easily worked around by using the constructor that takes a TextFieldValue as value, but should be fixed nonetheless.

I would be very interested in the reporter's "easy workaround" using the TextFieldValue constructor. How does that work? When I'm trying to use it, I'm only able to enter one char as a user and no more...

I hacked around the issue in the following way:

Before:

// asyncSource comes from the View Model and is changed via `changeText()`
OutlinedTextField(
    value = asyncSource.data,
    onValueChange = {
        viewModel.changeText(it)
    }
)

After:

// asyncSource comes from the View Model and is changed via `changeText()`
var inputText by remember(asyncSource.data) { mutableStateOf(asyncSource.data) }
OutlinedTextField(
    value = inputText,
    onValueChange = {
        inputText = it
        viewModel.changeText(it)
    }
)

I recognize that this is actually duplicating some of the logic, but I didn't have the jumping cursor issue anymore and still retain all flexibility of using asynchronous handling in my View Model and as a data source for the UI.

Hi, this is a 2020 bug which has undirectely been pointed out also in this -> https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5 article which actually cites the solution of the last user and is written by a Google spokeperson. It's a very spread one and impacts a LOT of developer and consequently a lot of user. It should be taken a little more seriously maybe. This fix is also not usable by kmm developers as pointed out inside a lot of comment of the above mentioned article and it's also very frustrating for people whose app has a lot or even more than 3 text fields.
Please, at least start to work on this issue.

Thanks for the comment.

The team already has started working on general structure of the TextField API since the current API and structure does not allow us to move forward with this ticket.

updated the assignee (one of Halil, Zach but can set only one), and also the priority to communicate that the work is ongoing in buganizer.

Yes, the work on this bug and related issues regarding TextField state was started a while ago. 1.5-alpha01 release includes some of this work.

It's unlikely that anything will be finalized in one release-cycle but the upcoming changes will be initially released as Experimental. So, the iterative changes won't be confined to alpha releases.

The solution in post #18 seems to work for me. Hoping this will be fixed soon officially.

Workarounds are outlined as per 18. The official solution is the new generation of TextField APIs which will be coming in future releases of Compose.

Comment 18 referenced this article: https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5

Closing this since async onValueChange updates are not supported and will continue to not be supported.

Yes: https://developer.android.com/jetpack/compose/text/user-input#state-practices

Also kind of implied by the kdoc but could be more clear.

It's also been explained in more detail in a few talks:

• around minute 26
• around minute 21

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

• androidx.compose.foundation:foundation:1.6.0-alpha08
• androidx.compose.foundation:foundation-android:1.6.0-alpha08
• androidx.compose.foundation:foundation-desktop:1.6.0-alpha08