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.

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 there, Our Password Manager app on macOS allows a user to unlock their password database using Apple Watch for convenience. We check that Apple Watch is available for use by calling canEvaluatePolicy in the usual way. This works really well most of the time, if the Watch is available, we'll be able to call evaluatePolicy to have the user authenticate with their watch. However, we have been receiving reports that when their watches go to sleep our App incorrectly requests they authenticate with their watch. It does this because canEvaluatePolicy returns true, but once we call evaluatePolicy instead of requesting the user authenticate, we immediately get an error: Error Domain=com.apple.LocalAuthentication Code=-1 "AppleWatch authentication failed." UserInfo={NSDebugDescription=AppleWatch authentication failed., NSLocalizedDescription=Authentication failure.} Apparently though there is a way to detect this, the Apple User Login screen is able to detect that the watch is asleep and requests a password instead. Also System Preferences that require a password somehow can cause the Apple Watch to vibrate when asleep but then fails gracefully/falls back to requesting a password. As developers, we would like to know if we can request Apple Watch authentication using the canEvaluatePolicy function. If the watch is asleep, then that should we believe return false. Any help or pointers on how to detect this scenario appreciated.

Hi, I have been receiving complaints from some users about 3-4 second delays in launch or simply activation of my app on iOS14 (all release versions). This only happens on iOS14, the same App Store binary/IPA does not exhibit this issue on iOS13. I have confirmed the issue myself but I'm not sure where to go from here? Is anyone else experiencing similar? Is this a known issue? Any tips on how to debug or otherwise raise this with Apple? I've tried profiling with Instruments/SceneKit/Activity Monitor - Nothing obvious shows up. If anyone from Apple is reading this, get in touch I can point you at the app in the App Store to reproduce. Thanks!