Failing to download swift package due to SSL error in Xcode Cloud.

Question

Failing to download swift package due to SSL error in Xcode Cloud.

BrentMifsud opened this issue 3 years ago · 5 comments

BrentMifsud commented 3 years ago

Steps to Reproduce the Problem

add instabug-SP as a dependency to your project
build in Xcode cloud

Expected Behavior

package should resolve successfully

Actual Behavior

xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://ios-releases.instabug.com/release/Instabug/10.8.0/archive.zip' which is required by binary target 'Instabug': downloadError("Error Domain=NSURLErrorDomain Code=-1200 \"An SSL error has occurred and a secure connection to the server cannot be made.\" UserInfo={NSErrorFailingURLStringKey=https://ios-releases.instabug.com/release/Instabug/10.8.0/archive.zip, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDownloadTask <106890B4-FE12-453D-B50C-68C53E5E2AD7>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(\n \"LocalDownloadTask <106890B4-FE12-453D-B50C-68C53E5E2AD7>.<1>\"\n), NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., NSErrorFailingURLKey=https://ios-releases.instabug.com/release/Instabug/10.8.0/archive.zip, NSUnderlyingError=0x6000016e3b40 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 \"(null)\" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, _kCFNetworkCFStreamSSLErrorOriginalValue=-9836, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9836, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: utun3, ipv4, dns}}, _kCFStreamErrorCodeKey=-9836}") fatalError

Instabug integration code

Make sure to remove your app token.

SDK Version

10.8.0

iOS Version

n/a

Device Model

n/a

[Optional] Project That Reproduces the Issue

Answer 1 · 2021-12-01T19:01:24.000Z

Also experiencing this. It is keeping our builds from succeeding on XCode Cloud.

Answer 2 · 2021-12-01T19:20:32.000Z

FYI, it is possible this is an issue with the trusted root certs on Apple's XCode Cloud servers, as Qualys gives each of the four SSL frontends an 'A'.

https://www.ssllabs.com/ssltest/analyze.html?d=ios-releases.instabug.com

Answer 3 · 2021-12-01T19:27:11.000Z

Filed issue with Apple as FB9790597.

Answer 4 · 2021-12-11T15:57:38.000Z

Hi @BrentMifsud
Sorry for the late reply, The issue mainly from Xcode cloud side as it's still beta, It's flaky now, but also we are contacting Xcode Cloud team to tell them about the issue. We will update you once it's solved
Thank you

Answer 5 · 2021-12-11T18:51:06.000Z

Hi @BrentMifsud

Sorry for the late reply, The issue mainly from Xcode cloud side as it's still beta, It's flaky now, but also we are contacting Xcode Cloud team to tell them about the issue. We will update you once it's solved

Thank you

No worries we had to stop using it for the time being because it's incredibly slow compared to GitHub runners and other CI (builds we're taking 3x as long as our GitHub runners were).

I'm hoping they get that settled before release. Not having to use fastlane alone makes Xcode cloud pretty attractive.