A workaround is to invoke the app dialog that allows credential selection (AppName....). That all works fine.

Submitted. FB12084416 The app is SamuraiSafe, but it's code is not executed prior to the exception being raised (I checked in the debugger), so I don't think it is app dependent. It is written in Objective C.

A workaround is to disable Source Control in settings. But defeats a major purpose of the editor.

Same here. XCode 14.2. Crashes every 5 minutes or so, with no input. Always: Crashed Thread: Dispatch queue: DVTSourceControlGitXPCClient :: Proxy Completion Queue

I did submit a big report with iOS 13 in 2020, but then was unable to recreate with iOS 13.5.1 to provide additional debug data. I have not seen the issue manifest itself recently (iOS 15). So sorry, didn’t have the energy to do so for the above incident.

Ditto. Code that works fine on iOS 12, 13, 14 and 15 (devices) fails on iOS 15 simulator. SecItemAdd returning errSecAuthFailed. kSecAttrAccessControl object has kSecAccessControlBiometryCurrentSet|kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly

I provide a solution here. It is not pretty. But it works.

I have the same problem with my password manager app. Setting the NSTextContentType to NSTextContentTypeOneTimeCode may help, although in my case this makes it only slightly less annoying. What is needed is a way to disable the behaviour completely. This is now available with UIKit on iOS (UITextContentTypeNewPassword). I have a couple of NSSecureTextFields and they don't all behave the same way. Some heuristics are in play to enable the behaviour. Better documentation from Apple would be appreciated!