Reachability.swift: No such module 'ReachabilitySwift

[mohamamdkalim]

Hello,

i am using xcode 9.1 and swift 3.2 always getting an error:

No such module 'ReachabilitySwift

in podfile:
pod 'ReachabilitySwift'

kindly let me know what can i do ... always getting an error

[eoinzy]

Its been renamed to just "Reachability".
Change the name in your Podfile and try again.

[NiltiakSivad]

I think @eoinzy is possibly installing the wrong library. It should definitely be pod 'ReachabilitySwift' in your Podfile. However, the import statement, should indeed be import Reachability.

Reference the CocoaPods installation steps in the documentation: https://github.com/ashleymills/Reachability.swift#cocoapods-1

If you're still getting errors after doing the above. I think this is a bug in xCode. I was getting a similar error running xCode 9.1 and Swift 4.0.2.

What I did to resolve:

1. Clean project
2. Close xCode
3. Open xCode
4. Rebuild project

After these steps, in xCode 9.1 the No such module error would still appear, but my build would succeed, and the references to ReachabilitySwift classes resolved fine.

I also tested on xCode 9.0 and the error was not reproducible there, it only appeared in xCode 9.1.

[547]

You just get into this directory: targets -> build settings -> linking -> other linker flags. Then, you can just replace the ReachabilitySwift with the Reachability.

[jobinsjohn]

@NiltiakSivad The issue is still happening after following your steps also.

[ghost]

@NiltiakSivad @547 @jobinsjohn The issue is resolved with " import ReachabilitySwift "

[Shagee08]

I'm having the same issue with FirebaseMessaging and Locksmith. Can someone please help?

[frankbfromh]

I ran into the same problem as described above. Turns out there were different deployment targets across the various targets. I set them all to the same version and the problem was solved.

[paulshapiro]

I believe this issue is caused by CocoaPods inserting an Other Linker Flag of -framework ReachabilitySwift due to the CocoaPod name of the module. Isn't that expected behavior and therefore the CocoaPod spec name is wrong, since the framework module is now called Reachability? i.e. even if we modified Other Linker Flags to "Reachability" to get it compiling, it's not a fix; CocoaPods will just generate the same thing again.

[paulshapiro]

Just a little more info on this. Carthage instructions cite a "ReachabilitySwift.framework" but CocoaPods is most definitely producing a "Reachability.framework"

[Allan-Nava]

@NiltiakSivad , I use your steps but I still have the same error:

[Akyya-Mayberry]

Issue still exists for me. I decided to use the other option which is just to drop the Realibility.swift file into my project.

[kamifernandez]

i solve with import Reachability
not import ReachabilitySwift

[hamchapman]

As many have stated you should be using import Reachability 👍

[mirkin]

I'm getting the same error, I can test on device but can't archive.

[bbo-jay]

It's still giving No such module 'Reachability'

[zilions]

I'm getting the same error as @mirkin. Able to test fine in the simulators, although when trying to archive the error is displayed.

The only way that I found to fix this was changing the deployment target from iOS 10, to iOS 11. Not ideal, although it's the only thing that worked for me.

[georgenimber]

I am having a similar issue with an app crash (symbol not found)
The app has both objective C Reachability and the Swift ReachabilitySwift.
Now that the ReachabilitySwift was renamed ,will I have an issue with both included ?