For Swift 4, shouldn't .swift-version
be updated accordingly? Currently it says 3
. :)
@couchdeveloper by the way, did it work for you when you tried to use import Reachability
instead of import ReachabilitySwift
?
I've just updated to Swift 4, but for me it compiles only when I import ReachabilitySwift
and not Reachability
(as described in a README). I specified ReachabilitySwift
in Podfile as well (according to README), specifying Reachability
downloads Objective-C version of the library.
@couchdeveloper You would think so, but I forgot to update the file, and it works fine for me. I assume that the .swift-version
file was only needed in Xcode 8 that shipped with 2 incompatible versions (2.3 & 3). The compiler for Xcode 9 can compile both Swift 3.2 & 4.
@application-developer-DA ReachabilitySwift
in the podfile is correct. I'll take a look at the framework naming issue.
Not sure, which tool actually utilises the .swift-version
file. As far as I know, CocoaPods (https://github.com/CocoaPods/CocoaPods/pull/5841) and Swift Version Managers, e.g.: swiftenv
.
@application-developer-DA We are using Carthage currently, so I cannot comment on that. (But notice, Carthage麓s dependency resolver is currently bugged: it resolves to 4.0-beta2
, when I set the version constraint to ~> 3.0
).
Most helpful comment
@application-developer-DA
ReachabilitySwift
in the podfile is correct. I'll take a look at the framework naming issue.