"Avoiding Common Networking Mistakes" (https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/CommonPitfalls/CommonPitfalls.html#//apple_ref/doc/uid/TP40010220-CH4-SW2) states that on iOS raw sockets are best avoided since, among other things, "using sockets directly using POSIX functions or CFSocket does not automatically activate the device’s cellular modem or on-demand VPN." Doesn't this caveat also apply to using libcurl on iOS?
Post not yet marked as solved
Btw, Technical Note TN2232 HTTPS Server Trust Evaluation still states the following (emphasis mine):"This code allows the connection if the trust result is either kSecTrustResultProceed or kSecTrustResultUnspecified. In most cases the result is actually the latter, indicating that the user hasn't specified a trust preference, so your app should do the default thing (that is, connect). The distinction between these two values is irrelevant on iOS [...]"; this should be updated also.
Post not yet marked as solved
Thanks Quinn, I know; and I agree: it probably is no bug. I just wish this subtle change of behaviour - as consistent with the API documentation as it may be - had been mentioned somewhere.
AFAICT this alert cannot be avoided, only customized in the same way the other features falling under "Privacy" can - by providing a suitable purpose string.
Thanks for the clarification. Does that mean that an app's access to Face ID will be controllable via the Privacy settings as for e.g. Location Services?
Post not yet marked as solved
Please keep in mind that https://developer.apple.com/ios/update-apps-for-iphone-x/ discourages this: "Avoid using icons to represent Face ID and Touch ID."
>In the simulator, the Face ID permissions alert will show "This app was designed to use Touch ID and may not fully support Face ID" if that key is missing. On an actual device, your app will crash the same as if any other required usage string is missing.Does that mean that an app which is in the store now - so it obviously misses the NSFaceIDUsageDescription key in its Info.plist - will crash on iPhone X if it is not updated in advance to include that key?
Post not yet marked as solved
> Will the documentation for this be available later or is only Local Authentication supported for Face ID?The new Face ID Security whitepaper (https://images.apple.com/business/docs/FaceID_Security_Guide.pdf) states:"Keychain items can also be protected with Face ID, to be released by the Secure Enclave only by a facial match or the device passcode. App developers also have APIs to verify that a passcode has been set by the user before requiring Face ID or a passcode to unlock keychain items."> what will happen with applications that currently are using for example kSecAccessControlTouchIDCurrentSet or kSecAccessControlUserPresence to limit access to keychain items?The API diffs (https://developer.apple.com/documentation?changes=latest_major) don't show changes in neither LocalAuthentication nor Security, so that's still unclear.
