We’ve been doing a bit of investigation into a discrepancy between the Swift version compatibility results for Alamofire on the Swift Package Index and what the intended compatibility is.
You state in your badges 5.3+ and have
Package@5.3 files, and sure enough, those all work fine, but we also get a successful build on watchOS with Swift 5.2 using
xcodebuild from Xcode 11.6. See the full build results here and a specific build for watchOS with Swift 5.2 on the 5.5.0 tag here.
I’ve verified our build results using
xcodebuild with Xcode 11.6 and the log you see on the build page above is what gets output. Of course, when you try and import the package into a watchOS app project with Xcode 11.6 you get an incompatibility warning:
We do get failures when
xcodebuild attempts to resolve dependencies with Swift 5.2 and other platforms (example).
We’d love for our package compatibility to be accurate as people are potentially making decisions from it but we’re struggling to figure out what’s letting the watchOS build succeed where the others fail and we wondered if you had any insight on what might be different for this build?
Of course, the easiest way for a package author to “remove” compatibility would be with an
#if and an
#error, which may be the best situation here too, but we’re interested if we can make any adjustments on our side before resorting to that.