User Profile

WKWebView’s createWebArchiveData method should invoke the completion handler with a Non-NULL Data which would contain the web-archive data of the web-page, or, a Non-NULL error if any error occurs. But instead, the method calls the completion handler with a NULL data and a NULL error. Other observations: In Swift, WKWebView’s createWebArchiveData method does return a valid result and the result.get() call does return a valid data. But passing this data to an UIActivityViewController as an Activity Item does not recognize the web-archive data. WKWebView’s createPDFWithConfiguration method works as expected.

WKWebView’s findString finds the string in the page but does not select and does not scroll to the selection automatically. Also, as mentioned in the article below, calling WKWebView’s select method with nil as argument enables selection of the string that’s found but still does not scroll to the selection. https://stackoverflow.com/questions/64193691/ios-wkwebview-findstring-not-selecting-and-scrolling

Hi,[EMERGENCY FIX NEEDED. ALL iOS 13.4 USERS ARE FACING FREEZE DUE TO THIS AND HAVE RATED THE APP NEGATIVELY]The 3rd Party Password Autofill feature provided by Authentication Services has a weird issue in iOS 13.4. we verified on iOS 13.3 and it works without any issue.I have reported a bug about the same with detailed video recordings that covers debugging the issue, which I will share with eskimo via E-mail.Bug Scenarios(Tapping on any of the suggestions on the quick suggestion, quick-type bar or on the suggestions that appear on tapping the "Key" icon):- I took time to debug this issue and found the following.- When the user taps on any of the suggested logins, the ViewController that extends the CredentialProviderViewController is loaded and the viewDidLoad is called as expected.- Once viewDidLoad is executed, viewWillAppear should get invoked but instead, viewDidLoad is invoked the second time. Not sure if the extension is being loaded twice or it is loaded once but the viewDidLoad is being invoked twice by the System.- After viewDidLoad is executed the second time, the flow is suspended. Nothing happens.- But, on tapping anywhere on the screen, viewWillAppear gets invoked immediately which is unexpected.- After viewWillAppear is executed, the Autofill Extension is launched and executes perfectly.Working scenarios(On tapping the application name on the Action sheet that pops-up on tapping the "Key" icon):- In this scenario, when the user chooses to open the Autofill Extension implemented by the App, the flow works perfectly without issues.- On tapping the "Application name" at the bottom of the Action Sheet that appears on tapping the "KEY" icon on the keyboard or the quick suggestion view, The Autofill extension of the App is launched perfectly without issues.- viewDidLoad is invoked.- Once viewDidLoad is executed, the flow continues to invoke viewWillAppear as expected and hence, the feature works perfectly fine in this scenario.Possible Issues:- viewDidLoad getting invoked twice and viewWillAppear never getting invoked unless the user taps anywhere on the screen.Thanks,Aravind Vaidhyanathan

Hi,Our application predominantly uses the keychain and the secure enclave to generate asymmetric keys and decrypt using the secure enclave.When testing our application against iOS 13 beta for any compatibilty issues, we encounted a problem while decrypting using the Secure Enclave.We use SecAccessControlCreateFlags.biometryAny constraint to restrict accessing the private key only with a valid biometric registered on the device, and, this is what is actually causing the problem. When SecAccessControlCreateFlags.biometryAny is not set, the decryption succeeds.Below is the error that is thrown:Error Domain=CryptoTokenKit Code=-3 "setoken: unable to compute shared secret" UserInfo={NSLocalizedDescription=setoken: unable to compute shared secret}keyType: kSecAttrKeyTypeECSECPrimeRandomaccessibilityProtection: kSecAttrAccessibleWhenUnlockedThisDeviceOnlyaccessControlFlags: SecAccessControlCreateFlags.biometryAny.rawValueDecryption Algorithm: eciesEncryptionCofactorX963SHA256AESGCMThis whole feature works perfectly on all other versions of iOS below 13.0.Please let us know if this is a known issue, or, if you have any suggestions to overcome this.Thanks,Aravind Vaidhyanathan