'No such module' when I use CocoaPods

Question

So here's my procedure. I create a new Podfile in the project directory, then I added the following

platform :ios, '9.0'
use_frameworks!

target 'CPod' do
pod 'AFNetworking', '~> 2.5'
pod 'ORStackView', '~> 2.0'
pod 'SwiftyJSON', '~> 2.1'
end 

I fire off pod install, and everything goes well, open up the xcworkspace. I then go over to ViewController.swift and if I try to import a pod I get No such module 'SwiftyJSON', if I were to do import SwiftyJSON. Any ideas?

EDIT: SwiftyJSON is a Swift based module, not Obj-C

Chopin

possible duplicate of Swift: Cannot use library from Pod file – Orthogenesis

That would be the case for AFNetworking , but that's a different story. SwiftyJSON is a Swift library, therefore that post doesn't answer the question. @Orthogenesis – Chopin

which version of cocoapods are you using? – Mentholated

I believe it it 0.37.2 @MichaelDautermann – Chopin

@Chopin had the exact same issue. May be an Xcode 6.3.2+ problem. – Devito

I'm running on Xcode 7, so that might be an issue, doubt it though. @Devito – Chopin

Any luck? Im running xcode 6.4 just installed cocoapods and tried using it. None of my pods can be imported. platform :ios, '8.0' use_frameworks! target 'QContact' do pod 'SwiftyJSON', '~> 2.2' pod 'SwiftAddressBook', '~> 0.4' pod 'MaterialKit', '~> 0.3' pod 'DynamicBlurView', '~> 1.0' end target 'QContactTests' do pod 'SwiftyJSON', '~> 2.2' pod 'SwiftAddressBook', '~> 0.4' pod 'MaterialKit', '~> 0.3' pod 'DynamicBlurView', '~> 1.0' end – Trivandrum

Upgrade to Xcode 7, its out now @Trivandrum – Chopin

You don't need to use "import SwiftyJSON" right? It's already included in the project when added in the header file. I never got both obj-c and swift pods working in my projects though. Impossible as far as I know. It's either only obj-c pods or swift pods. – Chiquia

This solved it for me: https://mcmap.net/q/204944/-no-such-module-39-restkit-39-with-cocoapods-and-swift – Supernal

Answer 1

Try adding the Pods framework to your build scheme and building the framework. After you've built it, build/run your project.

Steps:

1. Scheme menu > Manage Schemes > check Pods > Close

2. Select Pods from the scheme menu.
3. Build Pods.
4. Select your project from the same menu, then build/run it.

Bilbo

You rocked it! Thank you for this :) – Critic

In Xcode 11.0 it is now under Product -> Scheme -> Manage Schemes – Pier

I don't have pods at all. What should I do? – Portfolio

Similarly, another tip would be check that you've selected the correct scheme for your project. I had accidentally changed to an alternate scheme and got this error. – Gillett

Black magic: my usual scheme was broken. So I selected some other random one, builds ok, but doesn't launch simulators. I now switch back to usual scheme: everything works again! – Gat

@Portfolio I was able to see Pods after selecting .xcworkspace instead of .xcodeproj – Straw

This is basically a miracle this solution, thanks a lot bro it saved so much time for me! – Mitrailleuse

Answer 2

You must reopen project .xcworkspace file(not .xcodeproj) after install your podfile.

1. Clone the repo with CocoaPods
2. Open YourWorkspace/YourApplication.xcworkspace
3. Select the app u want to run Add SwiftyJSON.framework in embedded binaries for that project Hit Run

Happy Coding :)

Mussel

THANK YOU!! this was exactly what I needed. I had no idea about workspaces and had always been opening the xcodeproj file. – Inness

Worked great for me! Thank you! – Garvy

Real trick here is don't open "project .xcworkspace" from the command line and make sure that xcode and any emulator are closed. When you open xcode, you should see "your project" with a blue icon and "Pods" as another project also in blue. – Unsteel

@Unsteel I guess they get confused because their names are similar. It happened to me tried first time. :) – Mussel

Some solutions are so simple that sometimes I really think they aren't work. In my case, your solution helped me to figure out that I wasn't opening the .xcworkspace file because I double clicked at my Framework directory. It's a kinda weird behavior from Xcode, but it happens. – Embryologist

@MarcosRocha I'm really glad to hear that. Can you up to my solution. Maybe we can help more. :) – Mussel

Answer 3

You may also try re-installing pods using:

pod deintegrate

and then

pod install

This fixed this issue for me

Leafstalk

sometimes it's necessary to run these commands twice... Additionally I've run rm -rf ~/Library/Developer/Xcode/DerivedData/* command – Dan

I did this and then build the pod scheme and the library scheme then it work. – Rimskykorsakov

Such a simple solution and I didnt think this will work. But it did. Thanks – Eccrine

this worked for me as well. I tried deleting pods, podfile.lock, .wcworkspace, installing a newer version of cocoapods, I've tried it all and only this worked. Thank you ! – Kaffiyeh

Answer 4

Press Command+Option+Shift+K and then Run your app, you will see a magic.

Or from the menu -> Product, press Option on your keyboard and you'll see Clean Build Folder.

It's looking funny that how could Xcode do those things with us but same thing happened to me when I used a Swift library using Pod and after too much struggle I ended up with Clean Build Folder.

Hecklau

Of all the hundreds of solutions out there for the 'No such module' error after installing pods in an Xcode project, this is the only one that actually works for me. +1. – Stringpiece

Forgot about the age-old addendum where you switch something off and then on again and it works. SIGH. – Agadir

Answer 5

Not sure if this would still be helpful for others. But, in my case, it ended up being a silly mistake of not referencing dependencies from the .podspec file.

We have an application with multiple internal libraries, and those libraries also have dependencies on each other - which we accounted for the in the Podfiles... but NOT in the podspecs.

So, even though our Podfiles had:

Application / Podfile

# Development Pods
pod 'ConsumingLibrary ', :path => '../ios-consuming-lib'
pod 'DependentLibrary1', :path => '../ios-library-one'
pod 'CommonCoreLibrary', :path => '../ios-common-core-lib'

ConsumingLibrary / Podfile

# Development Pods
pod 'DependentLibrary1', :path => '../ios-library-one'
pod 'CommonCoreLibrary', :path => '../ios-common-core-lib'

Needed to also call it out in the .podspec's:

ConsumingLibrary / ConsumingLibrary.podspec

  # TODO
  # Add here any resources to be exported.

  s.dependency 'DependentLibrary1', '~> 0.1.0-RC'

DependentLibrary1 / DependentLibrary1.podspec

  # TODO
  # Add here any resources to be exported.

  s.dependency 'CommonCoreLibrary', '~> 0.1.0-RC'

I think I wasted about 2 hours trying to figure out why I could build ConsumingLibrary & run tests, but as soon as I built the app, that consumed all three libraries - I kept getting:

No such module 'DependentLibrary1'

Raptor

Two libraries are having a dependency on each other. Is it not going to give us circular dependency issue? I am currently facing this issue. Do you know how to resolve this? – Seen

@Raptor you are a godsend. This was exactly my issue. Thank you immensely!!! – Cicatrize

Answer 6

In my case it was because I opened xcodeproj instead of the correct xcworkspace.

Descendant

yes, it was my case. Thanks! – Vachill

Answer 7

Had this issue, too. I noticed the folder in Pods/broken_framework_name for framework which produced an error was empty even after pod install or pod update. So, for me those steps helped:

1. close XCode completely
2. remove DerivedData
3. remove Podfile.lock. Before doing it, make sure your pods are set to specific versions and it will not cause unwanted code updates
4. run pod deintegrate
5. remove .xcworkspace file
6. probably optional step: I had general line use_frameworks! written before all targets, but included it also in target in which I had an error
7. run pod install

After all steps I noticed missing framework files finally appeared back and build was working again.

Comeau

Be careful with removing the Podfile.lock. If any pods aren't set to use a specific version you could end up updating all your pods and need to then refactor your project. This may be fine on new projects but for legacy projects it could mean spending a few extra hours updating your codebase. – Flameout

@RobB, thanks for the note, but removing Podfile.lock is too often operation and it must not ruin your codebase. It must never happen that pods versions in your Podfile are set so badly. It shouldn't update to next major/minor version without you to change it specially. – Comeau

I totally agree with you. However, that is the best case scenario. Most codebases I come across don't follow best practices and don't properly set those values. In a perfect world you wouldn't have to worry about it. – Flameout

Hm, yeah, here I agree. Added warning to the post. – Comeau

Removing the .xcworkspace file and then calling pod Install was the crucial step for me! – Dip

Answer 8

Try using pod update after pod install command which will solve problem of No such module. I just tried and it working fine.

Thanks, Ratneshwar

Stevenstevena

Answer 9

Those who working with multiple targets , please don't forget to add this line in pods

def shared_pods
    pod 'SSKeychain', '~> 0.1.4'
    pod 'INAppStoreWindow', :head
    pod 'AFNetworking', '1.1.0'
    pod 'Reachability', '~> 3.1.0'
    pod 'KSADNTwitterFormatter', '~> 0.1.0'
    pod 'MASShortcut', '~> 1.1'
    pod 'MagicalRecord', '2.1'
    pod 'MASPreferences', '~> 1.0'
end

target 'Target_Name' do
    shared_pods
end

target 'Target_Name_Two' do
    shared_pods
end

Furriery

oh Boy, you saved my life. thank you ! Note : If you haven't done any pod modification since you created your targets, everything will work fine, until you perform a pod update, which just happen to me. – Exoteric

Answer 10

Sometimes happens when you have an obj-c pod within a swift project (even when you use the use_frameworks! in the .podfile).

If you're sure the pod is installed and you are still getting No such module, try this:

• Go to Pods project in Xcode
• Pods
• Right click on the affected pod
• Show in finder

There should be a package file with .framework suffix. Create a folder Modules in it. In this folder create a file called module.modulemap with code:

framework module MODULE_NAME_HERE {
  umbrella header "MODULE_NAME_HERE.h"

  export *
  module * { export * }

  link framework LINKED_FRAMEWORKS_AND_LIBRARIES_THE_POD_NEEDS_HERE
  link framework "AdSupport"
  link "c++"
  link "z"
}

Rebuild and you should be ok.

Giselle

Answer 11

As @jakub-truhlář wrote, the root issue is the missing module.modulemap file due to some concurrency issue mixing Swift and Objective-C libraries, but instead of creating those files manually, would be better to try multiple times cleaning the Derived Data and build your project. When the project is successfully built then commit module.modulemap files to your repository to avoid to lose those files for example changing the current branch.

Parnassian

Answer 12

i fixed it by check "Find Implicit Dependencies" to true. Go to Edit Scheme -> Build Tab -> set Find Implicit Dependencies = true.

and rebuild.

Therewith

Answer 13

I faced the same problem in a swift framework I developed. The framework had a dependency of git project and the framework itself added as a pod to my main project. So, ideally the dependency has been specified in podspec file and Podfile as well.

I didn't faced the problem when accessing through the my main project but when I open the framework standalone it was throwing "No such module" error.

The root cause is, the base configurations is set with the path which points towards my main project instead of the framework itself because I ran podinstall first in my main project and then in the framework project.

Eg: in the project file it was like 0091AB0C861D71C94ADD7240 /* Pods-myframework.release.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-myframework.release.xcconfig"; path = "../../Apps/MyMainProject/Pods/Target Support Files/Pods-myframework/Pods-myframework.release.xcconfig"; sourceTree = ""; };

After doing the below mentioned fix, 4444F5B1B35F066E57F96782 /* Pods-myframework.release.xcconfig */ = {isa = PBXFileReference; includeInIndex = 1; lastKnownFileType = text.xcconfig; name = "Pods-myframework.release.xcconfig"; path = "Pods/Target Support Files/Pods-myframework/Pods-myframework.release.xcconfig"; sourceTree = ""; };

To fix the error,

1. Project file -> Configurations -> Set all the configurations set to none.
2. Remove Pods folder and Podfile.lock.
3. Run 'pod install' first in the framework project direcory and then do pod install in main project directory.

Horny

Answer 14

I get some warning when pod install: '... target overrides the FRAMEWORK_SEARCH_PATHS build setting defined in ...'.

Fix it and enjoy.

Reference: target overrides the FRAMEWORK_SEARCH_PATHS build settings.

Formic

working for me with a pod in local path, thanks! – Poorly

Answer 15

Another way this issue can manifest: if you have multiple targets with different platforms (e.g. iOS and watchOS) you need to make sure your podfile specifies the correct platform for each target. Otherwise Cocoapods might be building the right pod but for wrong platform, leading to the "no such module" error.

You can fix it just by specifying the correct platforms e.g.

# global platform
platform :ios, '11.0'

target 'My Framework' do
  use_frameworks!

  pod 'RxSwift', '~> 5.1'
end

target 'My Framework (watchOS)' do
  # override global platform for this target
  platform :watchos, '4.0'

  use_frameworks!

  pod 'RxSwift', '~> 5.1'
end

Gregoire

Answer 16

For me, removing the following from my podFile fixed it:

      installer.pods_project.build_configurations.each do |config|
    config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
  end

Selfexpression

Answer 17

Adding link "c++" in the framework module.modulemap file worked for me

Rock

Answer 18

I had this problem when I opened XCode and then selected the workspace of my project via file->open recent.

I found that I had two .xcworkspace files on my filesystem for the same workspace/project.

Opening XCode by double clicking on the correct .xcworkspace file did the trick. The correct one is the one that works.

I later deleted the wrong one.

Zippora

Answer 19

I just updated particular dependencies in terminal

Go to project folder then run below command

pod update your pod name

For me I need to do

pod update ReachabilitySwift

Inspector

Answer 20

Had this issue while adding CocoaPods into an old project, which already had manually included libs from before. It happened because Xcode was not resolving to the Framework Search Path generated by CocoaPods because of values previously set in target's settings.

Solution that helped me:

1. copy the old path

2. hit delete to completely clear the Framework Search Path settings in the target's column - the path, generated by CocoaPods would appear there

3. add the old search path back under the generated one (only needed if you still have some manually added frameworks to work with)

4. Clean project, wipe Derived Data, build.

The result would look like this (1st line added by Xcode, 2nd added by CocoaPods, and 3rd is manual):

Madelinemadella

Answer 21

In case of multiple targets. For eg. Target1, Target2

use_frameworks!

target 'Target1' do
 pod 'Fabric'
 pod 'Crashlytics'

   target 'Target2' do
   end

end

Then run pod install.

Glosseme

in your code these targets are nested. Is it ok? – Ruzich

Answer 22

I tried all of these suggestions but nothing worked for me. Instead what'd worked for me was deintegrating pods. Afterwards deleting the pods folder from xcode hierarchy and doing pod install. Suddenly it worked. Don't ask me why because anyways most of these suggestions are hit or miss anyways but I'll be happy if it works for someone else too :)

Lindley

Answer 23

Make sure to import correct framework name that is defined in .podspec of the pod.

Summerville

Answer 24

My setup

• macOS 10.14 Mojave
• Xcode 10.3
• cocoapods 1.7.5

None of the answers work for me, although some gave partial clues. In my case, the root cause was that I customized my build product paths after running pod install.

If you run cocoapods right after creating an Xcode project, then it usually works if you open the generated Xcode .xcworkspace instead of the .xcodeproj.

Funny things happen if you start tweaking your build product paths after generating the workspace. Because the generated Pods project and its target all refer to your old Xcode project settings.

In my case, my trouble came from:

• I prefer all my build products sitting under the project folder $(SRCROOT)/build/$(CONFIGURATION)/$(EFFECTIVE_PLATORM_NAME). So I went ahead and changed my Pre-configuration Build Products Path to it .... AFTER doing pod install.

Now, the generated Pods project, including all its Framework target, still points to the old location, so both the header import and linking of your own project will fail (you'd see Command PhaseScriptExecution failed with a nonzero exit code when No such module is fixed).

The fix:

• Delete all Pods stuff including the workspace.
• Regenerate Pods project and workspace with pod install. However, cocoapods hardcodes the build product path to ${SRCROOT}/../build and Pre-configuration Build Products to $(BUILD_DIR)/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME) in my case, which usually points to a temporary ~/Library/Developer subfolder . Still not quite right. Then ....
• Make sure the Framework Search Path and Header Search Path of my own project cover the above paths.
• Tweak Pods project setting and all dependency Framework's Pre-configuration Build Products Path to use my preferred paths.

The moral lesson: Always regenerate Pods and verify the key result paths whenever you touch paths in Xcode project settings.

UPDATE

With Xcode 11, Apple finally removed the confusing "Pre-configuration Build Products Path". To customize the build product paths, use Locations in Xcode preferences with global relative paths pre-baked.

Loosestrife

Answer 25

I usually remove Pods folder and .xcworkspace file, then I run pod installagain and it helps in almost 100% cases.

Fieldwork

Answer 26

If you see this warning:

[!] The `Joint [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-Joint/Pods-Joint.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Joint [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-Joint/Pods-Joint.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

follow the instructions to avoid Module not found issue.

Nickerson

Answer 27

• clean project
• close xcode
• open xcode
• enjoy

Hoagy

Answer 28

For using Swift in Objective-C, you should import a header file that Xcode generates automatically in compile time (NameOfModule+Swift.h). In this case, you should try import SwifityJSON in you header file like this:

#import "SwiftyJSON-Swift.h" 

Majoriemajority

use_frameworks! you don't need to import the Obj-C header, you import the module, also the OP is using swift where do you see the need to import into Obj-C? – Aubrette