How to detect when user used Password AutoFill on

问题:

I've implemented all the app and server changes necessary to support Password Autofill on iOS 11, and it works well. I'd like it to work a little better.

My username and password fields are UITextFields. I would like to identify when a user has "autofilled" one of the two UITextFields, so I can progress to the next step. Currently the user autofills an item, then needs to press the "Next" button on the on-screen keyboard in order to advance. I'd like to trigger this on behalf of the user.

The WWDC2017 Password Autofill session says to use UITextFieldTextDidChange. This works, but of course this is also triggered when a user is manually typing in those fields.

My thought has been to compare the prior version of the text with the new version of the text, and assume that if the length has increased from zero to greater than some minimal length (2 or more), the user used autofill. That should work most of the time, but has a risk of a false trigger (fast typing on slow device perhaps). So to me, this may be a risky assumption.

I'm curious is anyone has found a more surefire way to determine if Password Autofill has been used on a UITextField, or just thinks my worry about a false trigger is unfounded.

回答1:

Not sure if the previous answer stopped working at some point, but I can't get it to work—I only get a single didBeginEditing call when AutoFill is used.

However, I did find a way to detect AutoFill. And keep in mind that it is possible for AutoFill to be used after some characters have already been entered, for example if the user has already typed some numbers in the phone number, then they AutoFill the full number.

For Swift 4:

var rangeReplacedWithSpaceAt: Date?

var rangeReplacedWithSpace: NSRange?

func textField(_ textField: UITextField, shouldChangeCharactersIn range: NSRange, replacementString string: String) -> Bool {
    // To detect AutoFill, look for two quick replacements. The first replaces a range with a single space.
    // The next replaces the same range with the autofilled content.
    if string == " " {
        self.rangeReplacedWithSpace = range
        self.rangeReplacedWithSpaceAt = Date()
    } else {
        if rangeReplacedWithSpace == range,
            let rangeReplacedWithSpaceAt = self.rangeReplacedWithSpaceAt,
            Date().timeIntervalSince(rangeReplacedWithSpaceAt) < 0.1 {

            DispatchQueue.main.async {
                // Whatever you use to move forward.
                self.moveForward()
            }
        }
        self.rangeReplacedWithSpace = nil
        self.rangeReplacedWithSpaceAt = nil
    }
}

回答2:

Found a solution.

When the password manager is used to autofill username + password, it will trigger didBeginEditing twice, faster than a human ever could.

So, I calculate the time between the events. If the time is extremely fast, then I assume that autofill (e.g. FaceID or TouchID) was used to enter credentials and auto-trigger whatever UI is next -- in my case, the User tapping "Sign-in".

Obviously, you have to set up the correct delegation of the UITextFields you want to monitor, but once you do that:

var biometricAutofillTime: Date!

func textFieldDidBeginEditing(_ textField: UITextField) {
    if biometricAutofillTime != nil {
        if Date().timeIntervalSince(biometricAutofillTime) < 0.1 {
            // NOTE: Need to hesitate for a very short amount of time,
            //        because, otherwise, the second UITextField (password)
            //        won't yet be populated
            DispatchQueue.main.asyncAfter(deadline: .now() + 0.2) { self.didTapSignin() }
        }
        biometricAutofillTime = nil
    }
    biometricAutofillTime = Date()
}

回答3:

I don't think there is a better solution.

One thing I noticed is that autofill is only enabled when the text field is empty.

So if the text field went from empty to a length greater than the minimum password/username, then it is most likely autofill/paste.

I am using shouldChangeCharactersIn to detect the change in the UITextField. I'm not for sure if there is a case where text from the keyboard could be batched together before the delegate method is called.