Post not yet marked as solved
When using password autofill on Safari 17.1 (Sonoma 14.1 on M1 Mac), and a third party password manager, the quicktype bar doesn't appear.
However on an Intel Mac with the same version of Sonoma and same Autofill configuration, it works as seen on Ventura.
Feedback assistant report has been submitted (FB13333122).
Post not yet marked as solved
My team and I manage 12 mobile applications and these are white-label applications. The company offers a web app equivalent to the mobile app, and we only have one client with a website and a mobile app right now.
The web app version of the app is hosted as a subdomain of the company's website, like app1.company.com and the plan for the other apps is to continue to host them as subdomains of the company's domain, like this: app2.company.com, app3.company.com, etc.
We would like to add the iOS Autofill feature for all apps so users can save their login credentials in their Keychain. Users can download more than 1 app, there is no restriction on that, and the user can have different login credentials for each application.
Can the domain have multiple Apple App Site Association files for each app subdomain?
Post not yet marked as solved
Any extension views called from ASCredentialProviderViewController -> open func prepareInterface(forPasskeyRegistration registrationRequest: ASCredentialRequest) cannot be rotated (to landscape). Is it a known issue or I am missing anything? Please suggest. Thanks!
Post not yet marked as solved
As announced for iOS 17 and macOS Sonoma, “One-time verification codes you receive in Mail are filled in automatically, so you can log in without leaving Safari.”
Is there any documentation about this? Maybe for a specific keyword that must be in the HTML email body? I tried it on my website with a verification code sent by email and it didn't work.
Post not yet marked as solved
Hi,
Does anyone know how to see or configure the period during which Safari honors biometric confirmation for autofill?
I've looked at the settings in bioutil but they don't align to what I'm seeing.
I frequently have to use my password to autocomplete Safari autofill for logins/passwords. If I use it in the morning, I'll have to go back to using the password once again by afternoon.
bash-3.2# bioutil -r -s
System Touch ID configuration:
Touch ID functionality: 1
Touch ID for unlock: 1
Touch ID timeout (in seconds): 172800
Operation performed successfully.
bash-3.2# bioutil -r
User Touch ID configuration:
Touch ID for unlock: 1
Touch ID for ApplePay: 1
Effective Touch ID for unlock: 1
Effective Touch ID for ApplePay: 1
Operation performed successfully.
Post not yet marked as solved
what could be the reason that we after saving and deleting the same list of [ASPasskeyCredentialIdentity], the credential still show up in the OS UI (quick type bar or when tapping the password key icon on top of the keyboard).
does that mean the remove operation fail? but our log indicate that the removeCredentialIdentities completion closure succeed without error.
and for the ASPasskeyCredentialIdentity initialization, we fill in the parameters from the same object, so we believe the id parameter shall be the same (which identify the same ASPasskeyCredentialIdentity to be saved and removed)
what could be the reason that it is still showing up in the OS UI? is this a know issue?
Post not yet marked as solved
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.
Post not yet marked as solved
As per apple documentation we are setting textContentType with "" in order to disable password auto fill view option on keyboards which is working fine in all iOS versions below 17 beta.
Seems like it broke & password auto fill view option appearing on keyboards for iOS 17 beta versions even on setting textContentType with "" & inputAccessoryView as nil
self.username.textContentType = @"";
self.password.textContentType = @"";
Post not yet marked as solved
Hi guys,
I am trying to get webcredentials for associated domains to work on a standalone watchOS-app that I am working on.
The AASA-file is hosted correctly, and the keychain autofill works fine on the iOS-app within the same workspace using the same associated domain.
The setup on the watchOS-app is close to identical to the iOS-app. The textContentType-modifiers are correctly added onto the textfields. Within the watchOS-app, the textfields allow me to browse my keychain but it doesn't filter the credentials linked to my associated domain.
The developer docs say:
For watchOS apps, you must add the Associated Domains capability to the WatchKit Extension target.
I assume that this doesn't apply to standalone watchOS-apps that do not have the WatchKit Extension.
Has anyone encountered this issue? Appreciate any ideas.
When using password autofill on Safari 16.4 (Ventura 13.3 on M1 Mac), and a third party password manager, when the proposed credential is selected an exception dialog appears.
This is new behaviour since the 16.4/13.3 update.
Touch id may be on or off - same result.
Traceback from exception:
Exception Name: NSInvalidArgumentException
Description: -[WBSCredentialIdentityMatch autoFillPasskey]: unrecognized selector sent to instance 0x600003bd3f00
User Info: (null)
0 CoreFoundation 0x000000018928719c __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000188da64d4 objc_exception_throw + 60
2 CoreFoundation 0x000000018932e178 -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x00000001891ef150 ___forwarding___ + 1600
4 CoreFoundation 0x00000001891eea50 _CF_forwarding_prep_0 + 96
5 Safari 0x00000001b3ffc7b4 -[FormAutoFillCompletionControllerObjCAdapter shouldShowAuthenticationSheetForCompletionListItem:] + 136
6 Safari 0x00000001b3ffa770 -[FormAutoFillCompletionControllerObjCAdapter performActionForListItem:result:shouldAbortCompletion:] + 44
7 Safari 0x00000001b3ff04e8 _ZN6Safari32FormAutoFillCompletionController29performSelectedListItemActionERNS_33FormAutoFillCompletionShouldAbortE + 84
8 Safari 0x00000001b3ffb844 -[FormAutoFillCompletionControllerObjCAdapter menuTableView:mouseUpInRow:] + 56
9 Safari 0x00000001b3f0dbe0 -[MenuTableView mouseDown:] + 312
10 AppKit 0x000000018c5ce474 -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 3476
11 AppKit 0x000000018c5590dc -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 364
12 AppKit 0x000000018c558d9c -[NSWindow(NSEventRouting) sendEvent:] + 284
13 AppKit 0x000000018c5580e0 -[NSApplication(NSEvent) sendEvent:] + 1556
14 Safari 0x00000001b3dc6f64 -[BrowserApplication sendEvent:] + 496
15 AppKit 0x000000018c7a80f0 -[NSApplication _handleEvent:] + 60
16 AppKit 0x000000018c41f57c -[NSApplication run] + 500
17 AppKit 0x000000018c3f69a8 NSApplicationMain + 880
18 Safari 0x00000001b412daa8 SafariMain + 408
19 dyld 0x0000000188dd7f28 start + 2236
michaelr.
