IssueTracker

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

I setup this modifier:

@OptIn(ExperimentalComposeUiApi::class)
fun Modifier.autofill(
    autofillTypes: List<AutofillType>,
    onFill: ((String) -> Unit),
) = composed {
    val autofill = LocalAutofill.current
    val autofillNode = AutofillNode(onFill = onFill, autofillTypes = autofillTypes)
    LocalAutofillTree.current += autofillNode

    this.onGloballyPositioned {
        autofillNode.boundingBox = it.boundsInWindow()
    }.onFocusChanged { focusState ->
        autofill?.run {
            if (focusState.isFocused) {
                requestAutofillForNode(autofillNode)
            } else {
                cancelAutofillForNode(autofillNode)
            }
        }
    }
}

And use it like this:

val emailState = remember { EmailState() }
Email(
    modifier = Modifier.autofill(
        autofillTypes = listOf(
            AutofillType.Username,
            AutofillType.EmailAddress
        ),
        onFill = { emailState.text = it },
    ),
    emailState = emailState,
    onImeAction = { onForgotPasswordSubmitted(emailState.text) }
)

With these steps, autofill works for me.

@lo...@gmail.com comment#8

what version of compose are you using? I'm using latest alpha and the above doesn't work for me. 😭

Works perfectly fine on the latest stable and alpha versions. Did you check in my second comment if you enabled everything?

I believe so?

I copied the modifier and then used

modifier = Modifier.autofill(
        autofillTypes = listOf(
            AutofillType.Username,
            AutofillType.EmailAddress
        ),
        onFill = { emailState.text = it },
    )

on my text field.

The auto-filling works for me with the latest alpha version, but I'm never presented with the save dialog though.

I am having exactly same problem. Autofill works, but the Save dialog is never shown...

Any updates on this? I can't get LastPass to display at all. I can ONLY get the Google Auto-fill service to work

Same here, autofill in Jetpack Compose only works with the Google auto-fill service. When picking 1Password as the Auto-fill service in Settings, the debug log prints out:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

1.3.1 won't dialog prompt to save a password for me but will prompt to autofill for google.

As a workaround, you can wrap the TextInputLayout from a layout file to an AndroidView in compose.

@Composable
fun TextFieldView(
    modifier: Modifier = Modifier,
    textState: MutableState<String>,
    @LayoutRes layoutRes: Int,
    textChanged: () -> Unit = {},
) {
    AndroidView(
        modifier = modifier
            .fillMaxWidth(),
        factory = { context ->
            val layout = LayoutInflater.from(context).inflate(layoutRes, null)
            layout.findViewById<TextInputEditText>(R.id.tilET).apply {
                doAfterTextChanged {
                    textState.value = safeText
                    textChanged.invoke()
                }
            }
            layout
        },
        update = {

        }
    )
}

val EditText?.safeText: String get() = this?.editableText?.toString().orEmpty().trim()

<?xml version="1.0" encoding="utf-8"?>
<com.google.android.material.textfield.TextInputLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/til"
    style="@style/TextInput"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    android:hint="Username">

    <com.google.android.material.textfield.TextInputEditText
        android:id="@+id/tilET"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:autofillHints="username"
        android:imeOptions="actionNext"
        android:inputType="textNoSuggestions"
        android:selectAllOnFocus="true" />
</com.google.android.material.textfield.TextInputLayout>

<?xml version="1.0" encoding="utf-8"?>
<com.google.android.material.textfield.TextInputLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/til"
    style="@style/TextInput"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    android:hint="Password"
    app:endIconMode="password_toggle">

    <com.google.android.material.textfield.TextInputEditText
        android:id="@+id/tilET"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:autofillHints="password"
        android:imeOptions="actionDone"
        android:inputType="textPassword"
        android:selectAllOnFocus="true" />
</com.google.android.material.textfield.TextInputLayout>

I tried using similar to above example. But its not working & following logs are getting printed.

getAutofillClient(): null on super, trying to find activity thread getAutofillClient(): none of the 1 activities on com.xx@8b0a7bc have focus No AutofillClient for com.xx on context com.xxn@8b0a7bc requestHideFillUi(null): anchor = null

Autofill popup isn't shown because autofill is not available. Did you set up autofill?

1. Go to Settings > System > Languages&input > Advanced > Autofill Service
2. Pick a service

Did you add an account?

1. Go to Settings > System > Languages&input > Advanced
2. Click on the settings icon next to the Autofill Service
3. Add your account

setSessionFinished(): from ACTIVE to FINISHED; autofillableIds=null

Can anyone help

Please fix 1password and compose

Any update? It would be good to fix it asap, please.

Any update on this?

It can be overlooked since it is simple but one of the important convenience feature.

Autofill is currently listed as "In Focus" on our Public Roadmap. This means we're actively working on this feature and hope to have something to share soon.

Could you please post some updates on this?

• it is one year in the roadmap: https://developer.android.com/jetpack/androidx/compose-roadmap
• one CL abandoned more than a year ago: https://android-review.googlesource.com/c/platform/frameworks/support/+/2434079
• another CL is getting silent: https://android-review.googlesource.com/c/platform/frameworks/support/+/3009614

It is sad that almost 3 years after a stable release of Compose there is still no support for Autofill.

A quick update here -

We built autofill for 1.7 and found that we need to do some substantial rework of the semantics system before it lands (this is ongoing top priority - aiming for hopefully 1.8).

Turning it on caused a large performance drop app-wide. We're working on fixing that, and then will turn autofill on.

It's currently #1 item on all of prioritization for compose feature work. Will give more update when it's getting closer to landing.

See comment #31 for the latest update from our engineering team.

The majority of autofill CLs landed this week. It seems that the next alpha should have this :) 🤞

Will the new autofill solution solve the strict mode unsafe intent violation?

mentioned above in comment #28? https://issuetracker.google.com/issues/176949051#comment28

Details here: https://developer.android.com/reference/android/os/strictmode/UnsafeIntentLaunchViolation

#36 are you only currently interested in API shape feedback, or should I be filing issues for non performance related bugs?

I would love for the api shape to be the way it was with xml - a simple one lime flag

I agree. Adoption of the flags was not high. Adoption of this will be lower. Users blame the password manager not the apps that have not implemented the simple flags.

"I would love for the api shape to be the way it was with xml - a simple one lime flag"

Personally I care less about a 1 liner and more about versatility of the API.

The 1 liner is good if it doesn't limit what can be done.

First and foremost it should be an idiomatic API.

Hi Priti,

Thanks for reaching out. The new Autofill APIs were added to 1.8 and you should be able to use them. I tested our demo App and Autofill works with Google Password Manager and LastPass. Can you verify that you try out this sample?

@Composable
fun BasicTextFieldAutofill() {
    val autofillManager = LocalAutofillManager.current

    Column {
        Text(text = "Enter your username and password below.")
        BasicTextField(
            state = remember { TextFieldState() },
            modifier = Modifier.semantics { contentType = ContentType.Username},
        )
        BasicTextField(
            state = remember { TextFieldState() },
            modifier = Modifier.semantics { contentType = ContentType.Password },
        )

        // Submit button
        Button(onClick = { autofillManager?.commit() }) { Text("Submit credentials") }
    }
}

The entire demo is here:

Source: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui/integration-tests/ui-demos/src/main/java/androidx/compose/ui/demos/autofill/TextFieldAutofillDemo.kt;drc=8e2e6368a5c20346d75e909379c2d1045ea74111;l=94

Can you try this out and report back if it does not work?

#46 Is there some mechanism in autofill to differentiate different login/password combos for the password manager? In my app they can login to different servers they own for different services and I'd like to have some ways for the password manager to only shows the credentials relevant to the current service type.

#48 Then from the docs how "For example, if a user has already signed into your app through the Chrome browser on their laptop and saved their password through a credential provider, then their credentials are served to them through Autofill." works? Or how does Chrome to tell the password manager the current website he's browsing.

Like in my case the user have saved a password in Chrome for a website with an url, and in my application he configure to connect to that same website and the same url there's really no way from Compose to have that match? All I can offer to the users is that they save again all their login/password for their servers after entering them in my app, and then they will have the list of all entries for every server they add ?

#47: Tell us more about your use case. Did this work in a view-based app but doesn't work in Compose? If it did, what are the APIs you used for views?

Is this related to using setImportantForAutofill for the "service type" Dropdown? Or did the "service type" field have an autofill hint?

#50: This is good feedback. The document meant to point to the fact that if you have stored credentials, you can long press on a textField and then select one of your stored passwords. But it the way it is worded makes it look like there is a way to connect the web version of an app with the android version of the app. That's a good idea. We don't have this right now, but if you file a feature request we can send it over to the autofill team.

That use case is specific for a Compose app from start. Will stay with the basic support then.

For the feature request can do if you point me to the proper tracker category.

Project: platform/frameworks/support
Branch: androidx-main
Author: Ralston Da Silva <ralu@google.com>
Link:      https://android-review.googlesource.com/3499897

Introduce InputText Semantics Property

Introduce InputText Semantics Property 
 
TextFields have an EditableText semantics property which 
stores the text value after output transformation. Autofill 
needs access to the text value after input transformation 
but before output transformation. Adding this semantics 
property helps send the right information to the Autofill 
service. 
 
Bug: 395911609 
Bug: 176949051 
Test: Added new tests and updated existing tests 
Relnote: "Added a new semantics property InputText that captures 
a textfield's value before output transformation is applied." 
 
Change-Id: Iae46a52e7fbb1a3558e897c5afebd125089befbb

Tried out the latest sample but I'm unable to get the store password with commit to work. There is no popup prompted with 1.8.0-beta02. I set the password manager to be the Google Password Manager. Phone is Pixel 8 running Android 15. Is the sample incomplete?

In some scenarios username and/or password may be generated. E.g in our usecase we have a unique number that serves as the account and password, and there is no additional details needed such as email. The user interaction to create an account would be just pressing a button "Create account" that generates a new account. With the current API I what would be the recommended way to implement this? I see there being 2 options:

1. Upon successful account creation, set the semantic on a hidden TextField or TextField for login, before navigating away. (Feels it could be likely to race when set the property on a textfield just before navigating away)
2. When showing the account number after a successful account creation, set it semantic NewPassword and then do a LaunchEffect to commit. However this breaks the guideline of only calling commit on a button press.

For the scenario above, it would also be nice to have an options to disable the strong password suggestion. Because as mentioned the user does not get to select their password.

Edit: I finally made it work. One have to enable the "Offer to save passwords", in Google Password Manager.

Furthermore, you have to have both NewUsername & NewPassword content type on two separate fields, and seemingly the user have to interact with both fields in-order to offer the storage of a new login. E.g settings "username" and "password" to be default text in the field and the calling "commit" will not work, nor will it to programmatically modify these strings. An interaction with the view/keyboard has to happen.

I'm looking forward to hear if there is any way of programmatically just offering this, the current flow seems very complex for a lot of usecases.

Hi Meghan! Thanks for the quick reply.

This is the sample I was looking at: https://github.com/android/snippets/blob/cfeb99f00017b6166c7c2467b050ba58dd6d9cca/compose/snippets/src/main/java/com/example/compose/snippets/text/AutofillSnippets.kt#L82-L98

Regarding strong password: I see, I assume it shows this the knowing that it has to provide a password.

When using Google Password Manager, the save dialog will only appear when there is a NewUsername and a NewPassword field.

Is this the case for just Google Password Manager or all apps interacting with the autofill? Could a autofill provider choose to offer to save a Password without any user interaction and just "NewPassword" field?

We have this scenario in with our service. All our users sign up by pressing "Create account" we generate an account number to which they use as their login, users provide no email, username or password. Since the account is a generated value, we'd like to offer to save it in the users password manager so they don't forget it and have a nicer experience when logging in on other devices. I can also imagine other apps having similar solutions or generating the password to the user automatically.

Edit: I found the solution for my scenario, the usecase is not to go by the autofill service in this case, it seems like if you want to save a password w/o user interaction or with the help of the keyboard on should use the CredentialsManager.

Thanks for your reply & help Meghan

David @ MullvadVPN

I just tried it out. In a single text field it works now. But when I use for example two text fields and on IME action next on the first one I switch the focus to the next field via FocusRequester, the keyboards stays below the first text field and therefore hides the next one.

My assumption would have been that the keyboard would now automatically jump to the next, now focused field.

I guess the problem was partially fixed, tested on version version 1.2.0-alpha03.

Here are a few problems:

• The TextField does not get fully visible when using ImeAction (Previous or Next) and focusing in a TextField that is hidden under the keyboard
• The TextField does not get fully visible when the user types on the keyboard.
  • Considering the scenario that the TextField was visible when focused, and the user scrolls the screen and start typing while the focused TextField is hidden.

I think there is a mistake on the release note of 1.2.0-alpha03.

The release notes say that the behavior of adjustResize has been improved, but I think this is a mistake for adjustPan.

According to #55, we need to implement an API that doesn't exist yet to achieve the correct behavior with adjustResize, but that task still seems to be a WIP.

I actually tried it with the accompanist sample, but it only works well with adjustPan.

Added on 2022/03/02

I just looked at the release notes, and the description is now fixed. Thanks to the person who fixed it.

Concerning that workaround:

You can get rid of that hacky delay with an OnGlobalLayoutListener which will observe the actual IME rect size and will be triggered when the soft keyboard is fully visible.

A basic example could look like this:

val bringIntoViewRequester = remember { BringIntoViewRequester() }
val scope = rememberCoroutineScope()
val view = LocalView.current
DisposableEffect(view) {
    val listener = ViewTreeObserver.OnGlobalLayoutListener {
        scope.launch { bringIntoViewRequester.bringIntoView() }
    }
    view.viewTreeObserver.addOnGlobalLayoutListener(listener)
    onDispose { view.viewTreeObserver.removeOnGlobalLayoutListener(listener) }
}
OutlinedTextField(
    modifier = Modifier.bringIntoViewRequester(bringIntoViewRequester),
    ...
)

However additional view logic will be needed for it to work with multiple TextFields.

¯\_(ツ)_/¯

I'm currently using the following workaround :

@OptIn(ExperimentalFoundationApi::class)
// TODO Remove this workaround once they fix the issue
fun Modifier.bringIntoViewOnFocus(
    source: MutableInteractionSource? = null,
    extraOffset: Float = 0f,
): Modifier = composed {
    var layoutCoordinates by remember { mutableStateOf<LayoutCoordinates?>(null) }
    val requester = remember { BringIntoViewRequester() }
    val isKeyboardShown = LocalWindowInsets.current.ime.isVisible
    val isSourceFocused = source?.collectIsFocusedAsState()?.value ?: false
    val focusModifier = when (source) {
        null -> {
            val scope = rememberCoroutineScope()
            Modifier.onFocusEvent { state ->
                if (state.isFocused && isKeyboardShown) {
                    scope.launch {
                        requester.bringIntoView(layoutCoordinates, extraOffset)
                    }
                }
            }
        }
        else -> Modifier
    }
    if (isSourceFocused && isKeyboardShown) {
        LaunchedEffect(Unit) {
            requester.bringIntoView(layoutCoordinates, extraOffset)
        }
    }

    Modifier
        .onGloballyPositioned { layoutCoordinates = it }
        .bringIntoViewRequester(requester)
        .then(focusModifier)
}

@OptIn(ExperimentalFoundationApi::class)
private suspend fun BringIntoViewRequester.bringIntoView(
    coordinates: LayoutCoordinates? = null,
    offset: Float = 0f,
) {
    val position = coordinates?.size?.toSize()?.toRect()
    val adjusted = position?.copy(
        top = position.top + offset,
        bottom = position.bottom + offset
    )
    bringIntoView(adjusted)
}

You can pass in MutableInteractionSource or it will default to Modifier.onFocusEvent + an extra offset in case the bottom navigation gets in the way. I'm sure it's not the best solution but it seems to work ok. Usage :

val extraOffset = with(LocalDensity.current) {
    BottomHeight.toPx()
}
OutlinedTextField(
    value = "test",
    onValueChange = {  },
    modifier = Modifier.bringIntoViewOnFocus(extraOffset = extraOffset),
)

The method described in #70 seemed doesn't work if the Column has a verticalScroll in the modifier

I still have issue with 1.2.0-alpha05, ADJUST_PAN and Landscape Orientation :

@Composable
private fun Screen() {
    var textValue by remember {
        mutableStateOf("")
    }
    Surface(Modifier.fillMaxSize()) {
        Column(
            horizontalAlignment = Alignment.CenterHorizontally, verticalArrangement = Arrangement.Center,
            modifier = Modifier.fillMaxSize()
        ) {
            Text(
                text = "Title",
                style = MaterialTheme.typography.h4,
                textAlign = TextAlign.Start,
                modifier = Modifier
                    .fillMaxWidth()
                    .fillMaxHeight(0.3f)
            )
            Spacer(modifier = Modifier.height(4.dp))
            Text(
                text = "Text\nTwo line",
                style = MaterialTheme.typography.body2,
                textAlign = TextAlign.Start,
                modifier = Modifier
                    .fillMaxWidth()
                    .fillMaxHeight(0.2f)
            )
            Spacer(modifier = Modifier.height(16.dp))
            TextField(
                textStyle = MaterialTheme.typography.body2,
                value = textValue,
                onValueChange = {
                    textValue = it
                },
                modifier = Modifier
                    .fillMaxWidth()
                    .fillMaxHeight(),
                colors = TextFieldDefaults.textFieldColors(
                    backgroundColor = Color.Blue,
                    textColor = MaterialTheme.colors.onSurface,
                    focusedIndicatorColor = MaterialTheme.colors.onSurface,
                    unfocusedIndicatorColor = Color.Transparent,
                    cursorColor = MaterialTheme.colors.onSurface
                )
            )
        }
    }
}

Click on the TextField and the field will be behind the keyboard. Be sure to force the orientation in landscape :

<activity
            android:name=".MainActivity"
            android:configChanges="keyboardHidden|uiMode|screenSize|screenLayout|orientation|colorMode|density|fontScale|fontWeightAdjustment|keyboard|layoutDirection|locale|mcc|mnc|navigation|smallestScreenSize|touchscreen"
            android:exported="true"
            android:label="@string/app_name"
            android:launchMode="singleTop"
            android:screenOrientation="landscape"
            android:theme="@style/Theme.ComposeTextFieldLandscapeTest"
            android:windowSoftInputMode="adjustPan">

Is it expected or still a bug ? It works if we adjust a vertical padding on Column (basically if the TextField is small "enough", it will be displayed above the keyboard). Maybe the issue is that the field is too big to be displayed above so it doesn't "scroll" to it ?

I'll push my sample on Github if required.

What is the recommended workaround for this issue? I tried some of the ones posted above but it seems they have limitations and do not always work in my case.

The fix should be in for non-lazy column in 1.2.0-alpha06

As per https://developer.android.com/jetpack/androidx/releases/compose-foundation#1.2.0-alpha06

"TextFields will now be kept above the keyboard when they are focused and the keyboard is shown, when inside a non-lazy scrollable and the soft input mode is ADJUST_RESIZE. (I4a485, b/190539358, b/192043120, b/216842427)"

Compose status update: Please update the Status and Status Summary fields of this bug! (or Public Status/Public Status Summary)

1.2.0-alpha07 works for me even with WindowCompat.setDecorFitsSystemWindows(window, false) - I'm listening for insets in the activity and adding the ime ones as a bottom padding for the content FrameLayout findViewById(android.R.id.content).

My only question is how to specify an extra offset to scroll additionally when keyboard appears? Say you have a bottom navigation that may get in the way or implemented toolbar quick return pattern as the user scrolls and using offset on the scaffold content?

I can repro the case where adding newlines until the cursor goes below the IME does not cause a scroll, but that's a separate issue so I've filed it as b/229125238.

I can't repro the issue reported in #81. What device/android version/IME are you seeing this with?

Should I report #76 in another issue ? it still happens in 1.2.0-alpha07 ; basically the text still goes below the IME if the TextField is too large to be visible entirely in the Rect above the IME. I have a working sample in the comment.

Isn't that the same as b/229125238?

Ok I can repro #81 on my Pixel 3 – ADJUST_RESIZE, not fitting system windows. Will investigate.

Filed the issue in #81 as b/230756508.

This is unfair. Compose issues are getting worked on, and at a good pace (contrary to many AOSP core bugs).

This one was one of the more complex ones and I guess it was delayed due to priorities which to me seem more or less reasonable.

And Compose is very usable in production, we have already released several rather complex apps which use it extensively.

All issues we've run into with QA (including this one) were fixable with workarounds. Also Compose devs provide good support/advice on them in kotlinlang's slack #compose channel. And doing workarounds for Compose issues is a lot more easier/pleasant than doing ones for a View-based system.

Anyways, I think this is not the discussion for the issue tracker.

Powerful tools may come with a bit of a steep learning curve (and to be honest, Compose ain't all that hard), but once that's done, you benefit from amazing possibilities and powers.

Regarding bugs, I don't see how Compose is any more buggy than the View system. As with any complex project, bugs are simply inevitable. It is indeed a new thing, and may still need some work to mature, but that's why there's Compose/View interop.

I use Compose mainly and I barely have to fix anything. If I don't like a default behavior, I don't have to sift through a 1000-line Custom View Java file, but I can simply copy the underlying Composable function, which is usually very simple and easy to understand, and change whatever I want easily.

And yes, I've already produced some rather complex apps with Compose, and actually used it for some weird use cases that I think are simply too hard to be worth it with Views, and yet Compose helped me create them reliably and easily exactly as I wanted (and even more than I wanted) down to individual pixels and even the small nuances in animations, shapes, and behavior, with code that's maintainable, short, and dare I say it, beautiful.

And at the end of the day, if you don't like it, don't use it. Google did not force anyone to use Compose, and all of its hype is well-deserved, aired by the Android Developer community at large.

Anyways, this is not the place to fight over this. If you have anything to help with this specific issue, you're welcome to provide your feedback. Otherwise you can go on Twitter or Reddit and do destructive criticism as much as you please, while developers here are building the next big thing.

I don't have any updates about fixes yet, but I understand the frustration about this issue and it is definitely being worked on. It's not actually a P4 – the "Priority" field on buganizer is very misleading, it has a very specific internal meaning and interaction with other systems so we don't use it for actual prioritization for compose text issues. Unfortunately, the way we track actual priority is not visible externally.

I'm using 1.2.0-beta03 and trying to make this work for a TextField inside a Row.

Even while using one of the workarounds, the functionality doesn't work most of the time in landscape mode, and seems to not work in certain cases in portrait mode (perhaps when the keyboard pops up a second or later time and making certain types of edits).

@OptIn(ExperimentalFoundationApi::class, ExperimentalComposeUiApi::class)
@Composable
fun EnterText() {
    Row(
        modifier = Modifier
            .fillMaxWidth(),
        verticalAlignment = Alignment.CenterVertically,
        horizontalArrangement = Arrangement.Center,
    )
    {
        val relocation = remember { BringIntoViewRequester() }
        val scope = rememberCoroutineScope()
        var thoughts by rememberSaveable { mutableStateOf("") }
        TextField(
            value = thoughts,
            modifier = Modifier
                .weight(1f)
                .bringIntoViewRequester(relocation)
                .onFocusEvent {
                    if (it.isFocused) scope.launch { delay(300); relocation.bringIntoView() }
                },
            label = { Text(text = "Enter text") },
            keyboardOptions = KeyboardOptions(keyboardType = KeyboardType.Text),
            onValueChange = { newText ->
                thoughts = newText
            }
        )
    }
}

Nothing to announce yet, but we are working very actively on this.

Please try to fix this on Priority, as going for hit & trial several times with the code and even after that not getting the expected workable solution is frustrating.

Read the comment number 40. I use this workaround in production, with about 1M users.

I realized I never posted my workaround for this.

It's actually on an old version of Compose but used to work very reliably

    val relocationRequester = remember { RelocationRequester() }
    var focused by remember { mutableStateOf(false) }
    val ime = LocalWindowInsets.current.ime
    LaunchedEffect(focused) {
        if (focused) {
            var done = false
            while (!done) {
                if (ime.isVisible && !ime.animationInProgress) {
                    relocationRequester.bringIntoView()
                    done = true
                }
                delay(100L)
            }
        }
    }
    TextField(
        modifier = Modifier
                // ...
                .onFocusChanged { focused = it }
                // ...
    )

I'm not sure if it still works with latest version because I didn't need it in recent projects yet and I haven't been working on the other one for several months.

I first posted it in this slack conversation https://kotlinlang.slack.com/archives/CJLTWPH7S/p1625070469186300

Let's say I have a sticky footer (bottom navigation) , Now when I type the text field will go below the bottom navigation even though I want it to be above it , so please fix that as well !

#112 you think it's worth creating a new issue with a repro on that and we can link to this bug if they're related? just to add to the test cases to verify

#113 Yeah , great !

This code doesn't work when OutlinedTextField becomes Multiline in a simple scrollable column https://gist.github.com/wakaztahir/12145df72c53ebc6e1a6feca46fbc3bc#file-testtextfieldcompose-kt-L38

I have a question , Do I need to use BringIntoViewRequester or the textfield will be kept in view without me writing any code ? Like Do I need to do anything ?

Hi there. This issue is not dead, and it is not fixed in production yet. It remains high priority for us and we're actively working on fixing it. However it is caused by a very complex combination of dependencies and the fix is not trivial. We've most recently been focusing on https://issuetracker.google.com/issues/195049010 and https://issuetracker.google.com/issues/259274257 blocking this specific bug. https://issuetracker.google.com/241591211 is also related. TY.

Major fixes to this were just released in 1.4.0-alpha04. Text fields in lazy columns should work now too. One notable case that is still being worked on is if the text field is bigger than the available space.

You mean an OutlinedTextField? Can you share the snippet?

Can you please attach a video of BasicTextField still going under the IME? And repro code if possible.

Ah, that's https://issuetracker.google.com/237190748. Still working on that one.

I am getting the same crash , waiting for next release , please release that fast

Major fixes to this were just released in 1.4.0-alpha04

Major bugs were also released...

    java.lang.NoSuchFieldError: No static field $stable of type I in class Landroidx/compose/foundation/text/KeyboardActions; or its superclasses (declaration of 'androidx.compose.foundation.text.KeyboardActions' appears in /data/app/~~xxx/base.apk)
        at androidx.compose.material3.TextFieldKt$TextField$5.invoke(TextField.kt:343)
        at androidx.compose.material3.TextFieldKt$TextField$5.invoke(TextField.kt:323)
        at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:107)
        at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:34)
        at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider(CompositionLocal.kt:228)
        at androidx.compose.material3.TextFieldKt.TextField(TextField.kt:323)

The crash above is reported here with workaround: https://issuetracker.google.com/265172081#comment2 , TY

so I upgraded to material 3 alpha04 and now I am not getting the Crash BUT I am still getting the text field going under the keyboard , I will post a video about it My TextField does take full width , is multiline but unless the user presses enter , it remains single lined , When I tap on the text field , the keyboard comes from underneath and stays on top of the field I don't use BringIntoViewRequester or any other code to bring it into view , I expect it to work magically.

Can you confirm you're also using Foundation version 1.4.0-alpha04? The bug was fixed in Foundation, not Material, and while material3 1.1.0-alpha04 should be using the latest alpha, I just want to make sure it actually is in your project. A video would be helpful, thanks.

I created a sample project and recorded this video , apparently the keyboard is opening and text field staying above when I tap on the field but not for long , when the text field becomes multiline , the text goes below keyboard

This project using latest compose version

1.1.0-alpha04 for material 3

Compose version 1.4.0-alpha04 , UI , which should probably including foundation of the same version

https://github.com/wakaztahir/captain-text-field

That's also https://issuetracker.google.com/237190748.

So if I apply a fixed height , would it work ?

Actually I think this might be a separate bug, since the resized field isn't internally scrollable. I filed b/266094055 to track.

We are closing this issue since the main case for this bug has been fixed: fixed-size text fields inside scrollable Columns and LazyColumns will be kept above the keyboard when they gain focus and the keyboard becomes shown and would otherwise cover the field.

There are still some cases related to this that are still broken and being worked on, but those will be tracked in separate bugs going forward. The known remaining issues at this time are:

• Cursors in text fields that take all available space and are internally scrollable may disappear behind the keyboard (b/237190748)
• Text fields that grow taller while being edited aren’t kept above the keyboard (b/266094055)
• Crash with “No field $stable of type I in class Landroidx/compose/foundation/text/KeyboardActions” (b/265172081)
• Text fields will stay below the keyboard when inside LazyVerticalGrid (b/265352893)

Please follow those individual bugs for further updates.

If you find new issues, please file new bugs instead of commenting here.