Autofill

RSS for tag

Streamline your app's login and onboarding procedures.

Posts under Autofill tag

134 Posts

Post

Replies

Boosts

Views

Activity

Autofill verification codes received in Mail
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.
4
4
4.9k
Oct ’23
Safari Password Autofill biometric validity period
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.
0
0
769
Oct ’23
ASCredentialIdentityStore.removeCredentialIdentities does NOT remove the credential as expected
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?
7
1
1.5k
Oct ’23
wkWebView, Trusted Domain, and Autofill/KeyChain Issue
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.
3
0
2.4k
Sep ’23
In iOS 17 Beta4 : how can I disable password autofill accessory view option?
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 = @"";
1
1
1.8k
Aug ’23
Associated Domains AutoFill on watchOS stand alone app
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.
0
0
1.1k
Jul ’23
Password autofill on Safari 16.4 raises exception
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
4
2
2k
Jun ’23
Apple ID
Apple ID Good morning! We have a published App. We are trying to update. We do not change anything in the existing login process in the app that is already published. However, we are being refused by requesting the user's email when he logs in by Apple ID. In our App, our customers can register any email they want and not just their Apple ID email. How can we go about approving the update of our App that already works this way in the Apple Store?
0
0
938
Apr ’23
An autofill notification/callback when the user enters new credentials?
Our app suite supports autofill through the ASCredentialProviderViewController API, and it works well. We would like though to be also able to record a new login/password when the user enters them directly in his web browser, so that we can offer the pair for autofill the next time he opens the same page. Is there any API for that? Perhaps I'm just blind, but I can't find any. Thanks!
0
0
1.4k
Apr ’23
Closure error, Keychain
Hello everyone, I am fairly new to Swift and I've been working on a couple of things recently. Even after changing .textContentType(.username) and .keyboardType(.emailAddress), the autofill function still does not work for my project. I thought of changing and updating the whole Keychain class and started to use this wrapper https://auth0.github.io/SimpleKeychain/documentation/simplekeychain/. The class that I use to handle user's data uses an old objective-c class (oldKeychain) with different functions. func load() -> Promise<(String?, String?, String?)> {         return Promise { seal in                   // Load user password                   oldKeychain.loadCredentials(forKey: userPasswordKey, reasonString: "") { (errorCode, email, userPassword) in                       if errorCode == errSecSuccess {                         // Load device password                           oldKeychain.loadCredentials(forKey: self.devicePasswordKey, reasonString: "") { (errorCode, _, devicePassword) in                               // Device password is optional, may not exist                               seal.fulfill((email, userPassword, devicePassword))                         }                     }                       else {                         if errorCode == errSecUserCanceled {                               // Biometrics cancelled                             seal.reject(AppError.keychainBiometricsCancelled)                           } else {                             seal.reject(AppError.credentialsLoadUserPasswordFailed)                       }                     }                   }             }         } After changing the old reference to old class and calling different function the code structure would possibly look like this. func load() -> Promise<(String?,String?,String?)> {         return Promise { seal in             // Load user password             do {                 let value = try simpleKeychain.string(forKey: userPasswordKey) {(errorCode, email, userPassword) in                     if errorCode == errSecSuccess {                         // Load device password                         let value = try simpleKeychain.string(forKey: devicePasswordKey) { (errorCode, _, devicePassword) in                             // Device password is optional, may not exist                             seal.fulfill((email,userPassword,devicePassword))                         }                     }                     else {                         if errorCode == errSecUserCanceled {                             // Biometrics cancelled                             seal.reject(CVAppError.keychainBiometricsCancelled)                         } else {                             seal.reject(CVAppError.credentialsLoadUserPasswordFailed)                         }                     }                 }             }         }     }     However I keep getting Extra trailing closure passed in call error in this section of code let value = try simpleKeychain.string(forKey: userPasswordKey) {(errorCode, email, userPassword) in I tried to return just one value which did not throw any build errors but I have to be returning all 3 (email,userPassword,devicePassword). Does anyone have any tips on how to rewrite the code so that I do not get any closure errors and can return all 3 parameters with the use of new wrapper ? THANKS !!!
0
1
932
Feb ’23
Autofill doesn't work properly
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?
2
1
4.2k
Feb ’23
Autofill Password & iCloud Security Password Emptied/Reset Password TextField
Hello Everyone, we are experiencing this same problem recently and could not come up with a solution. Basically the problem is that when autofill password is enabled and the same for the option in the preference to save the security password via iCloud we have the same problem posted by the OP in this thread: https://developer.apple.com/forums/thread/716589?login=true&page=1#744911022 After filling the password field when we move to our confirm password field, the iOS system shows the same action sheet attached from the OP (String password or Other Options) and if we choose the Other Options action and then Choose My Own Password both field (Password & Confirm Password) will be emptied. We have already tried the suggestions provided in the thread linked above but nothing seems to work. Is this a normal behavior and we as engineers have the responsability to cache the password typed by the user when dealing with iCloud security password & autofill password preferences options or is this a strange behavior? Thank you everyone for the time, if you have any further question don't esitate to ask
0
0
1.2k
Feb ’23
iOS auto-fill password feature: development with dev server behind VPN
Hi, I'm trying to implement IOS auto-fill feature and I followed the documentation - enable autofill and shared we credentials setup. But before going to production, I need to test it in the development environment where the web is behind VPN. Here is my setup: development server https://dev.mydomain.com behind VPN verified thatapple-app-site-specification is reachable in path https://dev.mydomain.com/.well-known/apple-app-site-specification (connected to VPN) apple-app-site-specification content "webcredentials": { "apps": [ "appteamid.com.mybundle.id", "appteamid.com.mybundle.id.dev" ] } } Xcode associated domains webcredentials:dev.mydomain.com?mode=development ipa signed by our development profile (verified can be installed on developer device) ipa distributed via private repo sharing (not Testflight) and it's not working :(. questions: does it have to be distributed by Testflight? if it could be distributed by private repo should it there be appteamid.com.mybundle.id or should be com.mybundle.id (without appteamid) does the domain have to be publicly available (could it be the problem that this is behind VPN)? any other suggestions why it is not working? thanks for any info
1
0
1.4k
Feb ’23
Passkey username autofill doesn't show up
I'm trying to implement Passkey support for my app and was able to implement the registration and modal login flow. However, the username autofill just doesn't show up. I also tested with Shiny demo app and got the same result. Is there anything I need to do for it to work? So far: Domain entitlement is added and working (registration and modal login works) Registered Passkey shows up correctly in Settings > Passwords Password Options > Autofill Passwords is on and set to autofill from Keychain Checked that the input field has textContextType: username Checked that performAutoFillAssistedRequests() was called before the input is focused Tested on simulator (XCode 14.1, iOS 16.1) and iPhone 12 (iOS 16.1.1). Both were not showing autofill (no QuickType bar).
1
0
2.2k
Jan ’23
[Crash][16.1.X+] Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x10bbe6250> that is already being presented by <UIKeyboardHiddenViewController_AutofiIl: 0x1202f8c70>.
There is a crash on the iOS version 16.1.x. that impacts all the applications that manage password fields Here are 3 related crash logs linked to the same issue. The pre-requisites to reproduce the crash are to have: an iOS version 16.1.X+ an application that handles only Portrait or Landscape mode. How to reproduce the crash: Tap on an email or password field, and the keyboard opens and displays the 🔑 button If it's Portrait only, position the device in Landscape mode (and vice-versa) - Make sure to turn off the Portrait Mode Lock on your device Tap on the 🔑 button 🔴 You should have the crash The following reports are strongly linked to this one. iOS16 autofill causes crash while click "key button"(over keyboard) Application tried to present modally a view controller <_SFAppPasswordSavingViewController: 0x11fb2ac60> that is already being presented by <UIKeyboardHiddenViewController_Save: 0x118f7fde0>.
0
1
2.2k
Dec ’22
ios16+ crash. Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x119e2fae0> that is already being presented by <UIKeyboardHiddenViewController_Autofill: 0x119e2fe80>.
Hi, I'm working on iPhone APP with iOS16.1.1 or iOS16.1.2. If I use APP with the following steps: turn off portrait orientation lock and use APP under Landscape orientation click the password autofill bar on keyboard After the above, the Biometrics popups and then App crash. The crash information is: Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x119e2fae0> that is already being presented by <UIKeyboardHiddenViewController_Autofill: 0x119e2fe80>. Please help me out on how to solve this issue or let me know if I am missing anything.
0
1
1.7k
Dec ’22
WKWebView password autoFill suggested passwords section
Hey. I try to find out how to enable "suggested passwords" section for my keychain passwords. I've built a simple app with just a WKWebView that opens login page. When I tap on user name, passwords button appears above the keyboard. I tap on it and I see my passwords, but I don't see suggested passwords section for the website I have opened. That section definitely provides a better UX, as we don't have to scroll the page to find our password. I checked that on Safari, Chrome, Firefox, Opera and Brave. For all those apps suggested passwords section is in place. Do you have any idea how to enable it?
1
1
1.8k
Nov ’22
autocomplete="email" without email confirmation input
I am implementing a "login with email" feature i.e. the user enters her email address, I then send them a link, when the click it I authenticate them. I would like Safari to autofill the email address for the user but it always treats it as a username (but never gives the option to save the username). So basically Safari prompts the user to use a username from another website, instead of autofilling their email address in the email input. However if I ask the user to enter their email and display another box to confirm the email address, Safari correctly autofills the email. Is there a way to autofill a single "email" field on a form? Thanks
0
0
1.3k
Sep ’22
Autofill verification codes received in Mail
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.
Replies
4
Boosts
4
Views
4.9k
Activity
Oct ’23
Safari Password Autofill biometric validity period
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.
Replies
0
Boosts
0
Views
769
Activity
Oct ’23
ASCredentialIdentityStore.removeCredentialIdentities does NOT remove the credential as expected
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?
Replies
7
Boosts
1
Views
1.5k
Activity
Oct ’23
wkWebView, Trusted Domain, and Autofill/KeyChain Issue
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.
Replies
3
Boosts
0
Views
2.4k
Activity
Sep ’23
In iOS 17 Beta4 : how can I disable password autofill accessory view option?
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 &amp; password auto fill view option appearing on keyboards for iOS 17 beta versions even on setting textContentType with "" &amp; inputAccessoryView as nil self.username.textContentType = @""; self.password.textContentType = @"";
Replies
1
Boosts
1
Views
1.8k
Activity
Aug ’23
Associated Domains AutoFill on watchOS stand alone app
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.
Replies
0
Boosts
0
Views
1.1k
Activity
Jul ’23
Password autofill on Safari 16.4 raises exception
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
Replies
4
Boosts
2
Views
2k
Activity
Jun ’23
Apple ID
Apple ID Good morning! We have a published App. We are trying to update. We do not change anything in the existing login process in the app that is already published. However, we are being refused by requesting the user's email when he logs in by Apple ID. In our App, our customers can register any email they want and not just their Apple ID email. How can we go about approving the update of our App that already works this way in the Apple Store?
Replies
0
Boosts
0
Views
938
Activity
Apr ’23
An autofill notification/callback when the user enters new credentials?
Our app suite supports autofill through the ASCredentialProviderViewController API, and it works well. We would like though to be also able to record a new login/password when the user enters them directly in his web browser, so that we can offer the pair for autofill the next time he opens the same page. Is there any API for that? Perhaps I'm just blind, but I can't find any. Thanks!
Replies
0
Boosts
0
Views
1.4k
Activity
Apr ’23
Closure error, Keychain
Hello everyone, I am fairly new to Swift and I've been working on a couple of things recently. Even after changing .textContentType(.username) and .keyboardType(.emailAddress), the autofill function still does not work for my project. I thought of changing and updating the whole Keychain class and started to use this wrapper https://auth0.github.io/SimpleKeychain/documentation/simplekeychain/. The class that I use to handle user's data uses an old objective-c class (oldKeychain) with different functions. func load() -> Promise<(String?, String?, String?)> {         return Promise { seal in                   // Load user password                   oldKeychain.loadCredentials(forKey: userPasswordKey, reasonString: "") { (errorCode, email, userPassword) in                       if errorCode == errSecSuccess {                         // Load device password                           oldKeychain.loadCredentials(forKey: self.devicePasswordKey, reasonString: "") { (errorCode, _, devicePassword) in                               // Device password is optional, may not exist                               seal.fulfill((email, userPassword, devicePassword))                         }                     }                       else {                         if errorCode == errSecUserCanceled {                               // Biometrics cancelled                             seal.reject(AppError.keychainBiometricsCancelled)                           } else {                             seal.reject(AppError.credentialsLoadUserPasswordFailed)                       }                     }                   }             }         } After changing the old reference to old class and calling different function the code structure would possibly look like this. func load() -> Promise<(String?,String?,String?)> {         return Promise { seal in             // Load user password             do {                 let value = try simpleKeychain.string(forKey: userPasswordKey) {(errorCode, email, userPassword) in                     if errorCode == errSecSuccess {                         // Load device password                         let value = try simpleKeychain.string(forKey: devicePasswordKey) { (errorCode, _, devicePassword) in                             // Device password is optional, may not exist                             seal.fulfill((email,userPassword,devicePassword))                         }                     }                     else {                         if errorCode == errSecUserCanceled {                             // Biometrics cancelled                             seal.reject(CVAppError.keychainBiometricsCancelled)                         } else {                             seal.reject(CVAppError.credentialsLoadUserPasswordFailed)                         }                     }                 }             }         }     }     However I keep getting Extra trailing closure passed in call error in this section of code let value = try simpleKeychain.string(forKey: userPasswordKey) {(errorCode, email, userPassword) in I tried to return just one value which did not throw any build errors but I have to be returning all 3 (email,userPassword,devicePassword). Does anyone have any tips on how to rewrite the code so that I do not get any closure errors and can return all 3 parameters with the use of new wrapper ? THANKS !!!
Replies
0
Boosts
1
Views
932
Activity
Feb ’23
Autofill doesn't work properly
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?
Replies
2
Boosts
1
Views
4.2k
Activity
Feb ’23
Autofill Password & iCloud Security Password Emptied/Reset Password TextField
Hello Everyone, we are experiencing this same problem recently and could not come up with a solution. Basically the problem is that when autofill password is enabled and the same for the option in the preference to save the security password via iCloud we have the same problem posted by the OP in this thread: https://developer.apple.com/forums/thread/716589?login=true&page=1#744911022 After filling the password field when we move to our confirm password field, the iOS system shows the same action sheet attached from the OP (String password or Other Options) and if we choose the Other Options action and then Choose My Own Password both field (Password & Confirm Password) will be emptied. We have already tried the suggestions provided in the thread linked above but nothing seems to work. Is this a normal behavior and we as engineers have the responsability to cache the password typed by the user when dealing with iCloud security password & autofill password preferences options or is this a strange behavior? Thank you everyone for the time, if you have any further question don't esitate to ask
Replies
0
Boosts
0
Views
1.2k
Activity
Feb ’23
iOS auto-fill password feature: development with dev server behind VPN
Hi, I'm trying to implement IOS auto-fill feature and I followed the documentation - enable autofill and shared we credentials setup. But before going to production, I need to test it in the development environment where the web is behind VPN. Here is my setup: development server https://dev.mydomain.com behind VPN verified thatapple-app-site-specification is reachable in path https://dev.mydomain.com/.well-known/apple-app-site-specification (connected to VPN) apple-app-site-specification content "webcredentials": { "apps": [ "appteamid.com.mybundle.id", "appteamid.com.mybundle.id.dev" ] } } Xcode associated domains webcredentials:dev.mydomain.com?mode=development ipa signed by our development profile (verified can be installed on developer device) ipa distributed via private repo sharing (not Testflight) and it's not working :(. questions: does it have to be distributed by Testflight? if it could be distributed by private repo should it there be appteamid.com.mybundle.id or should be com.mybundle.id (without appteamid) does the domain have to be publicly available (could it be the problem that this is behind VPN)? any other suggestions why it is not working? thanks for any info
Replies
1
Boosts
0
Views
1.4k
Activity
Feb ’23
Passkey username autofill doesn't show up
I'm trying to implement Passkey support for my app and was able to implement the registration and modal login flow. However, the username autofill just doesn't show up. I also tested with Shiny demo app and got the same result. Is there anything I need to do for it to work? So far: Domain entitlement is added and working (registration and modal login works) Registered Passkey shows up correctly in Settings > Passwords Password Options > Autofill Passwords is on and set to autofill from Keychain Checked that the input field has textContextType: username Checked that performAutoFillAssistedRequests() was called before the input is focused Tested on simulator (XCode 14.1, iOS 16.1) and iPhone 12 (iOS 16.1.1). Both were not showing autofill (no QuickType bar).
Replies
1
Boosts
0
Views
2.2k
Activity
Jan ’23
Only username autofill on webview
Hi, does anyone know why autofill doesn’t work when there’s just a single username field? It works if there’s both username and password but not when it’s just the username. Strangely enough, it works fine when it’s just the safari browser but just not on webview
Replies
0
Boosts
0
Views
1.2k
Activity
Jan ’23
[Crash][16.1.X+] Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x10bbe6250> that is already being presented by <UIKeyboardHiddenViewController_AutofiIl: 0x1202f8c70>.
There is a crash on the iOS version 16.1.x. that impacts all the applications that manage password fields Here are 3 related crash logs linked to the same issue. The pre-requisites to reproduce the crash are to have: an iOS version 16.1.X+ an application that handles only Portrait or Landscape mode. How to reproduce the crash: Tap on an email or password field, and the keyboard opens and displays the 🔑 button If it's Portrait only, position the device in Landscape mode (and vice-versa) - Make sure to turn off the Portrait Mode Lock on your device Tap on the 🔑 button 🔴 You should have the crash The following reports are strongly linked to this one. iOS16 autofill causes crash while click "key button"(over keyboard) Application tried to present modally a view controller <_SFAppPasswordSavingViewController: 0x11fb2ac60> that is already being presented by <UIKeyboardHiddenViewController_Save: 0x118f7fde0>.
Replies
0
Boosts
1
Views
2.2k
Activity
Dec ’22
ios16+ crash. Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x119e2fae0> that is already being presented by <UIKeyboardHiddenViewController_Autofill: 0x119e2fe80>.
Hi, I'm working on iPhone APP with iOS16.1.1 or iOS16.1.2. If I use APP with the following steps: turn off portrait orientation lock and use APP under Landscape orientation click the password autofill bar on keyboard After the above, the Biometrics popups and then App crash. The crash information is: Application tried to present modally a view controller <_SFAppAutoFillPasswordViewController: 0x119e2fae0> that is already being presented by <UIKeyboardHiddenViewController_Autofill: 0x119e2fe80>. Please help me out on how to solve this issue or let me know if I am missing anything.
Replies
0
Boosts
1
Views
1.7k
Activity
Dec ’22
WKWebView password autoFill suggested passwords section
Hey. I try to find out how to enable "suggested passwords" section for my keychain passwords. I've built a simple app with just a WKWebView that opens login page. When I tap on user name, passwords button appears above the keyboard. I tap on it and I see my passwords, but I don't see suggested passwords section for the website I have opened. That section definitely provides a better UX, as we don't have to scroll the page to find our password. I checked that on Safari, Chrome, Firefox, Opera and Brave. For all those apps suggested passwords section is in place. Do you have any idea how to enable it?
Replies
1
Boosts
1
Views
1.8k
Activity
Nov ’22
autocomplete="email" without email confirmation input
I am implementing a "login with email" feature i.e. the user enters her email address, I then send them a link, when the click it I authenticate them. I would like Safari to autofill the email address for the user but it always treats it as a username (but never gives the option to save the username). So basically Safari prompts the user to use a username from another website, instead of autofilling their email address in the email input. However if I ask the user to enter their email and display another box to confirm the email address, Safari correctly autofills the email. Is there a way to autofill a single "email" field on a form? Thanks
Replies
0
Boosts
0
Views
1.3k
Activity
Sep ’22