Hi, We are receiving complaints from some users about our Password AutoFill component on macOS. The issue usually presents itself after some time, but it's pretty severe. When a user chooses our App to AutoFill their passwords, usually in Safari, we present a sheet allowing them to search from and choose a particular credential to fill. This works pretty well most of the time. However, after continued use, users report that they can no longer interact with the sheet using the mouse. Keyboard events seem to be fine, they can navigate using the up and down keys, but any clicks are just not registered. We've asked users to look in the console and let us know if they see anything strange. We've got a report back that Console is filled with: invalid display identifier <private> Also, it's speculative but all reports appear to be users using a second external display and it may possibly be related to the Mac going to sleep and the issue occurs after waking up. The solution for our users is to terminate Safari, upon restart the issue is resolved until the next time it begins, sometime later. Is there anything we can do, have you heard of an issue like this before, what could possibly block mouse events after a long period of time? Is this an App Extension issue, a Safari issue, a presenting a Sheet from an App Extension inside Safari issue? Any help appreciated.

Hi, we have developed password manager app that integrates with macOS Password AutoFill. This works well in Safari for filling passwords and users are happy. However users have reported that Safari keeps prompting users to save the just filled passwords in the Keychain. They receive a popup: Our users have explicitly and deliberately chosen not to use the Keychain for their passwords, so this is inappropriate. Unfortunately there appears to be no way to stop these prompts. You can turn them off only by completely disabling Password AutoFill in Safari, which means disabling our App's ability to AutoFill. This seems like an oversight. Setting here: Preferences > AutoFill > Usernames and Passwords Perhaps I've missed something, but if not, could we get a way to disable this Keychain/built in Password Manager prompt for users who use a third party Password Manager (which correctly works with Password AutoFill, the right way (tm) to do AutoFill). Cheers.

We have been searching for almost one year for answers as to why wkWebView using an Entitled Domain will allow Autofill with KeyChain to fill credentials, but will not trigger Autofill to store/save them. In other words, if users have previously stored credentials in Safari while visiting domain X, subsequent visited to wkWebView with entitled domain X will allow use of those credentials in wkWebView through the Autofill/Keychain dialogue. However, users cannot save/store credentials within wkWebView in Trusted domain X because the save dialogue is never triggered.

Hi, I've implemented the Username/Password AutoFill feature on the login page based on this article, but here is something weird. For example, if the text field is empty, the credential is pasted to the text field perfectly through iCloud keychain. If the text field is NOT empty, the credential cannot be pasted to the text field for the first time. Is it an iOS bug?

Hello, i want to build an app and the first question which comes to my mind is, how is it possible to create an automatic login to the landing page, if the user already logged in on his device? i hope someone can answer my question greetings Konstantin

We all know that post iOS 12, sms is automatically read by the textContentType = .oneTimeCode. However, we cannot recognise when it does that ( reading the otp from the sms) Is there any possibility of recognising the aforementioned state ( when the otp is read from the sms ) in any methods of the UITextField? There is a requirement where we need to save this as an event in an Event Tracking tool.

The Save Password / KeyChain dialogue is not presented upon entry of credentials in a wkWebView authorization view. While the domain is properly entitled and the KeyChain auto-fill does appear to FILL credentials that may already exist from Safari, the save user/password dialogue never displays on a change or if no prior credentials exist in Safari. Is this expected behavior? Clearly the entitlement of the domain allows the auto-fill to function properly.

We have the local data server for iOS application. I want to achieve passcode autofill. We cannot use Associated Domains, because AASA file is not settable local server. So, I would like to save the server secret in KeyChain and display the TOTP passcode generated by myself in the QuickType bar or autofill it. Is this feasible? Also, please tell me how to retrieve the secret key saved in KeyChain.

Hello, how I can enabled autofill (in suggestion type bar)code with will come in sms? What forma of sms should be? Thanks

I'm trying to do some form of autofill for a WKWebview on iOS and don't want to save CC info to our servers so I was wondering if I'm allowed to save it to the keychain if the user chooses to let us. I know at least one app seems to be doing something along those lines but I wanted to know if it's against ToS.