I have an Autofill Extension. It works well for the majority of the apps. For for a large number of applications it is called with an empty list of serviceIdentifers (ASCredentialServiceIdentifier). Which makes it impossible to auto detect the application bundle id. Why this varies from application to another. Shouldn't the OS automatically handle this?

Hello, Our macOS app includes a Password AutoFill extension and both the host app and extension have the entitlement for AutoFill Credential Provider. We have found that in Xcode 13 RC, when we attempt to archive our app using xcodebuild we receive this error: Cannot create Developer ID provisioning profile for "our.app.ID" The AutoFill Credential Provider capability is not available for Developer ID provisioning profiles. Disable this feature and try again. And a similar message for our extension's app id. We believe this to be a bug as building/archiving/submitting using Xcode 12 worked fine with this same entitlement. Otherwise, are non-Mac App Store apps now being excluded from including Password AutoFill capability? We've been shipping this feature to our customers in our Developer ID signed app since it first became available in macOS Big Sur. We'd appreciate it if someone could look into this right away, we have filed a feedback report: FB9634952.

Hello, I am trying to turn OFF autofill in Safari for an application. Is there any sure way to turn the autofill off on all devices? Safari is trying to autofill my Date of Birth field, email, and phone number but I do not want these fields suggesting autofill. Seems all other browsers have a way to completely turn it off now, besides Safari.

Hi everyone, Background:  We want to provide our customers with login with Facebook option It means - according to Apple policy - we must also implement login with Apple ID, and we are fine with it But - because of type of our business - we must collect from our customers also their mobile number.   First of all, it's their unique ID in our system (but of course we could change it, if it was necessary). But - what's more important - we are two-sided marketplace, we connect customers (pet parents) with business (vets, groomers, behaviourists, pet sitters etc.). Our merchants (business side) must have a direct phone number to their clients (customers side). When customers book a visit, we pass their mobile phone number to our merchants (with customers permission). It's because if anything bad happens (let's say, that vet by mistake gives a wrong medicine), they can react fast. Question: If we implement login/register with Apple ID, will we be allowed to ask additionally each our customer for their mobile phone? Regardless of their Apple ID settings? Simple rule: we didn't get customers phone number -> we ask them to set it. Also, important information might be, we validate it because we send SMS with validation code. Thanks in advance for your help, we are struggling with this since a while. Best regards Jakub

Context This is happening on both iOS 13.7/iPhone 11 and iOS 14.7.1/iPhone 11 Description I have a Sign up screen within my iOS app that has textFields with .username and .newPassword textContentTypes Strong password is suggested, and works to the extent that it gets set to keychain but the pop up that comes when password is suggested (the one that should have buttons with text "Use Strong Password" and "Choose My Own Password") only shows "Localized string not found" for all labels and buttons in there. I remember back in the day that these strings ("Use Strong Password" and "Choose My Own Password") appeared automatically with minimal configuration is this a known bug in iOS? Is there a workaround for this Is there some way to temporarily disable password autofill? Screenshot

Hello, Our application's Password AutoFill extension can no longer present its view when enabled in System Preferences panel for Extensions, or when selected in Safari's autofill menu, though it still appears there. Instead, an error from a private API is logged: +[NSExtensionContext _allowedItemPayloadClasses] not implemented. Setting the allowed payload classes to <private> If there's been any updates to the documentation about what our autofill extension is required to provide in terms of a list of allowed classes, I haven't found it yet. Does anybody know what's going on there, or have any suggestions? Thanks!

i currently have a Sign Up (registration) view with three text fields: Email Address, Password, and Confirm Password. The email address field has its textContentType set to .username, and both the passwords fields have it set to .newPassword. After entering the email address, tapping into the password field automatically autofills the password field with a strong password, but never autofills the confirm password field. The only way i have seen it autofill both password fields is if the user taps into the password field without entering an email address first. Since the email address field precedes both the password fields on the screen, it is unlikely the user will choose to enter a password first. Has anyone else experienced this, and if so, is there a way to get it to autofill both the password fields? This feature has been around since iOS 12 and i am experiencing this issue on iOS 14.6.

In WWDC2020, a new feature was introduced in which the app can get Contact AutoFill by setting the Content Type of a UITextFiled. This feature works on iOS 14.5 when the Content Type is set to email address but doesn't work for phone number. Here's the two changes I'm making in my code: textField.keyboardType = .phonePad textField.textContentType = .telephoneNumber Is there anything else that needs to be done or this is a known bug.

We have an issue to log into website with Face ID using AutoFill feature of Safari on iPhone. We are Not using the Web Authentication API with FaceID. Our website has multiple html buttons on sign in page (forgot username, forgot password, sign in).  When Face ID is used to AutoFill username and password and login into the website it uses the forgot username button which leads to forgot username page. So instead of using sign in button it uses forgot username button.  Is there a html property that needs to be set on the sign in button so face id knows it should use that one? STEPS TO REPRODUCE  Enable iCloud Keychain  Enable AutoFill for your Names and Passwords in Safari settings.  Open Safari and browse to website. Sign in as you normally would by entering your username and password. A message should pop up asking if you would like to save this password in your iCloud Keychain for AutoFill on all your devices. Tap on Save Password.  Sign out of the site  Try to Sign in using FaceID Using: IOS 14.4.1 Safari 14 iPhone 12 pro

Autofill not working in WKWebView I followed all the steps given here to enable autofill on my website. https://developer.apple.com/documentation/security/password_autofill/enabling_password_autofill_on_an_html_input_element After configuration, autofill working in the mobile Safari browser but not in the in-app-browser (WKWebView). May I know if this is supported by WKWebView. I don't see a save password prompt in the app but in the mobile safari browser it's working perfectly fine.

We are working on a banking application with sms authentication with otp. We have tagged our ITUextfields correctly with the type .oneTimeCode With some codes this is not being suggested on the keyboard as would be expected. In Messages app they are not suggested for copying either, but we don't know why. Aviso Bankia: Solicitado 27/05 consulta del PIN de tu tarjeta *0285 en Bankia Online. Codigo Firmamovil: 9N2U --&gt; suggested correctly Aviso Bankia: Solicitado 27/05 consulta del PIN de tu tarjeta *0285 en Bankia Online. Codigo Firmamovil: 9QNJ --&gt; It's not suggested Aviso Bankia: Alta de la tarjeta *285 en Apple Pay 28/05. Codigo Firmamovil: RB7V --&gt; suggested correctly Aviso Bankia: Alta de la tarjeta *028 en Apple Pay 29/06. Codigo Firmamovil: 9TVT --&gt; It's not suggested Aviso Bankia: Solicitado 27/05 consulta del PIN de tu tarjeta *0285 en Bankia Online. Codigo Firmamovil: 3T3E --&gt; suggested correctly Aviso Bankia: Solicitada consulta de CVV de su tarjeta ***0285 en Bankia Online. 28/05. Codigo Firmamovil: 8MQG --&gt; It's not suggested Thanks.