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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
All MGLMapboxEvents HTTP requests fail on iOS 9 with the following error:
Error Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x7fea5a771010>, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorCodeKey=-9802, NSUnderlyingError=0x7fea5a5d03d0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, _kCFNetworkCFStreamSSLErrorOriginalValue=-9802, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x7fea5a771010>, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9802}}, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., NSErrorFailingURLKey=https://cloudfront-staging.tilestream.net/events/v1?access_token=…, NSErrorFailingURLStringKey=https://cloudfront-staging.tilestream.net/events/v1?access_token=…, _kCFStreamErrorDomainKey=3}
Mapbox GL needs to adopt App Transport Security. See this blog post for details.
If I set NSExceptionRequiresForwardSecrecy=NO or NSExceptionAllowsInsecureHTTPLoads=YES for the cloudfront-staging.tilestream.net domain in the Info.plist, the errors go away.
Whoops, forgot to open a PR on this. In any case, 0178c94 exempts the Metrics staging server from the App Transport Security’s PFS requirement. That server should never be used in production code anyways: applications developed using Mapbox GL will use the normal Mapbox API server.
All MGLMapboxEvents HTTP requests fail on iOS 9 with the following error:
Mapbox GL needs to adopt App Transport Security. See this blog post for details.
/cc @bleege @kkaefer @incanus
The text was updated successfully, but these errors were encountered: