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
Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?
Confirmed reproduction steps with SwiftPM CLI.
Description
When fetch binaryTarget artifacts via HTTP, I get the error:
downloadError("The network connection was lost.")
Setting the proxy parameters no_proxy & http(s)_proxy does not affect the process in any way
Expected behavior
Success fetching through proxy
Actual behavior
error: failed downloading 'https://artifactory/dependency-binaries/mySDK-iOS-3.6.13.zip' which is required by binary target 'MYSDK-iOS-binary': downloadError("The network connection was lost.")
error: fatalError
Steps to reproduce
Swift Package Manager version/commit hash
5.9
Swift & OS version (output of swift --version ; uname -a)
swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx14.0
Darwin Ernest0-M1.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103 arm64
The text was updated successfully, but these errors were encountered:
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?Description
When fetch binaryTarget artifacts via HTTP, I get the error:
Setting the proxy parameters
no_proxy
&http(s)_proxy
does not affect the process in any wayExpected behavior
Success fetching through proxy
Actual behavior
Steps to reproduce
Swift Package Manager version/commit hash
5.9
Swift & OS version (output of
swift --version ; uname -a
)swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx14.0
Darwin Ernest0-M1.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103 arm64
The text was updated successfully, but these errors were encountered: