Try setting-up Domain Entitlement for the domain serving the webview and the app itself. I believe this security measure is required for wkWebView autofill.

This is working (partially) for us once Domain Entitlement is set-up. Password autofill/keychain will recognize the domain of the wkWebView that is associated with the App to deliver autofill/keychian/3rdParty password fills to properly attributed input fields (autocomplete="current-password" etc.) This only seems to work for autofill, and NOT for password saving. For whatever reason, the Save Password dialogue from iOS is not firing to save your credentials from wkWebView as it does in Safari. There seems to be no documentation from Apple on this. So, for a user to leverage saved passwords for an App with wkWebView, a user would have to sign in to the same domain via Safari, save their credentials, then open the App wkWebView and populate the fields. Again, there seems to be no way to save credentials from wkWebView even with domain entitlement enabled. Again, this is only apparent from attempts with POC builds. There still may be a way, and it would be great if Apple could respond to this question.

Also waiting for responses.

No joy on this topic from Apple. Awaiting any other responses.

Puzzling that this situation has remained unresolved and unanswered.

Matt, In an ASWebAuthenticationSession, using the default browser, we do not get the prompt to save/store passwords in keychain. Ironically, we DO get the autofill from keychain on subsequent visits IF we have the password stored from a regualr web session in Safari. What are we missing in terms of Saving credentials via the prompt in an ASWebAuthenticationSession?

Keep alive. I'm interested in an answer as well.

I wish someone would answer if this is supported; namely; does ASWebAuthenticationSession using the browser display a save prompt after credentials are added?

Does anyone use ASWebAuthericationSession to log into a web service for an App?