You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NSUnimplemented calls in URLCredential are, all but one, commented out. The commented out ones are there because the missing Security.framework in other platforms (there's API using SecIdentity, SecCertificateRef, SecTrust). I don’t think those can be removed without implementing equivalents to Security.framework.
The last one I think it is a mis-implementation. It happens in the initializer, where persistence is checked not to be .persistent or .synchronizable. However, I think the check should happen when the URLCredential is added to the URLCredentialStorage, not when creating it.
The type that is completely unimplemented is URLCredentialStorage. I haven't seen a parity bug for it, but I can tackle it at least for the temporal storage. The permanent storage probably needs help for each operating system, and the synchronized storage is probably impossible in most systems. Should I assign this bug to me or create a new one for that task?
Additional Detail from JIRA
md5: ead865f4acdb90867901864585388e5c
Parent-Task:
Issue Description:
The text was updated successfully, but these errors were encountered: