Tapping saved login does nothing a… | Apple Developer Forums

Tapping saved login does nothing after typing when .autocorrectionDisabled() or .textInputAutocapitalization(.never) modifier is applied

If a username field has .autocorrectionDisabled() or .textInputAutocapitalization(.never), tapping the saved login above the keyboard stops working once the user has typed part of their email. Nothing gets filled in. Seen on iPhone 16, iOS 27.0 (24A437).

I've also reported this to Apple through Feedback Assistant (FB24825410).

Steps to reproduce

You need an app with Password AutoFill set up (a webcredentials associated domain) and a saved login for that domain.

Tap the email field. The saved login appears above the keyboard.
Type a few letters of the email.
Tap the saved login.

Expected: the email and password fields fill in, replacing what was typed. Actual: nothing happens.

What works

A username field with only .textContentType(.username) and .keyboardType(.emailAddress). Tapping the saved login fills both fields, no matter how much the user has typed.

What breaks

With .autocorrectionDisabled(), the tap works after 1 typed character, but does nothing after 2 or more.
With .textInputAutocapitalization(.never), the tap does nothing after even 1 typed character.
UIKit has the same problem: a UITextField with autocorrectionType = .no behaves like .autocorrectionDisabled().

In all of these cases, choosing the login from the key icon's Passwords sheet still fills both fields. Only the tap on the suggestion above the keyboard fails.

Sample

struct LoginView: View {
    @State private var email = ""
    @State private var password = ""

    var body: some View {
        VStack {
            TextField("Email", text: $email)
                .textContentType(.username)
                .keyboardType(.emailAddress)
                // Either of these breaks AutoFill once the user types:
                .autocorrectionDisabled()              // fails after 2+ typed characters
                .textInputAutocapitalization(.never)   // fails after 1 typed character

            SecureField("Password", text: $password)
                .textContentType(.password)
        }
    }
}

Workaround

I removed both modifiers from our username field and it works. Typed emails still didn't get autocorrected in my testing.

Has anyone found a way to keep these modifiers on a username field without breaking AutoFill?