No such module 'RestKit' with cocoapods and swift

Question

I am having this problem with a brand new project. This problem happens with both RestKit and Facebook SDK. Strangely SwiftyJSON works just fine. I create a brand new swift project and a Podfile with:

source 'https://github.com/CocoaPods/Specs.git'

use_frameworks!

target 'test-fb-swift4' do
    pod "FBSDKCoreKit"
    pod 'SwiftyJSON', '~> 2.1'
    pod 'RestKit', :inhibit_warnings => true
end

target 'test-fb-swift4Tests' do

end

After creating that file I run pod install and reopen xcode with the test-fb-swift4.xcworkspace file.

Now inside my controller I put a import RestKit and I get the error No such module 'RestKit'. I have tried many different ways to format the Podfile even down to very simple versions like:

source 'https://github.com/CocoaPods/Specs.git'

pod 'RestKit'

I have tried adding and removing the use_frameworks, with and without the target. With and without the :inhibit_warnings.

I am running CocoaPods 0.36.4 and tried the latest rc build, same deal. The Objective-C version from another project runs fine. This is my first project using Swift and I am stuck on this issue.

Bosomy

Show how you're importing. – Decuple

Answer 1

I had the same problem. My solution was to open the project using the .xcworkspace, not the .xcodeproj. .xcodeproj only contains the main project; .xcworkspace includes everything including Restkit.

Ahner

i had to "save as Workspace" to get a workspace for a new project – Marvel

Glad I found this answer after more than 1 hour of searching. OP should really mark this as accepted. – Pushcart

Very ugly solution. The better way is to fix the issue: remove and add back Pods.framework on Target > Build Phases > Link Binary With Libraries. – Yemane

The OP said that they had already done this-- "After creating that file I run pod install and reopen xcode with the test-fb-swift4.xcworkspace file." – Achilles

Answer 2

I had a similar problem. Not with RestKit specifically, but initially with the HockeySDK. I tried everything, including removing and reinstalling pods, updating cocoapods itself and updating pods, deleting derived data, cleaning the project, etc.

I then noticed that every pod was an issue for me. After continuing to search on related topics, I finally discovered that under:

• Target > Build Phases > Link Binary With Libraries

I had a misplaced Pods framework (likely from a prior Pods setup or install attempt).

After removing it, the problem went away. I have noticed that people seemed to experience similar problems under:

• Project > Info > Configurations

as well, where the Pods framework was being mapped incorrectly. So if the first doesn't work for you, you may want to check on the second as well.

Cully

The second suggestion about build configurations was what caused this for me. I renamed my "Debug" build configuration on the app's project, but on the Pods project this created a new configuration instead of renaming "Debug". Deleting the "Debug" configuration from Pods project so that the configurations match those from the app's project solved it. – Paranoia

Answer 3

The second option worked for me. In my Project > Info > Configurations, I have 2 targets for my project : the regular one (Quizz) and the test one (QuizzTests):

For the regular one, the configuration was set with "Pods.debug" or "Pods.release" but there was none for QuizzTests. As soon as I filled in the configuration for QuizzTests, everything worked for me.

Rheims

Answer 4

For me, deintegrating and re-installing pods fixed the issue.

First

pod deintegrate

and then

pod install

Jasisa

This was a very simple solution, for some reason the others listed here did not work for me. May not matter, but make sure Xcode is shut down when deintegrating. – Mayhem

Same here. I had troubles after I rm -r'd my Pods directory, and re-installed with pod install, but pod deintegrate and pod install worked. – Shaveling

Answer 5

One thing you could very easily do to rectify this issue is to make sure that XCode is completely shut down when installing pods. Whenever I have this issue, I go back and find out that XCode was still open even though I closed the project. Hope that helps!

Pirouette

Very helpful, I was trying everything except this step. – Goeger

Yes, it is likely that if the pod install took place with Xcode open, then the frameworks are not initially visible. Simply closing and reopening the project fixed this for me. – Smile

Answer 6

Another potential solution that I found was to add use_frameworks! to your Podfile if you have not already and then run pod install again. It was an issue with Firebase when I added only that pod.

Czerny

Worked for me too. Seems I'd removed use_frameworks! from my Podfile and since I have a mixed Swift/Objective-C project the Swift part needed the frameworks included. – Stefaniastefanie

Answer 7

Another reason of this problem can be wrong values in target's Build Settings - Build Active Architecture Only. Settings like in the picture work for me.

Unfasten

Interesting, fixed for me too. I had changed this setting previously, but doing another pod install reset the value. – Hesler

Answer 8

For me, 'Find implicit Dependencies' was unchecked. and it was the issue. Worked fine once I checked it.

The path: Edit Scheme > Build > Find implicit Dependencies

Cosenza

THIS. I would upvote this a thousand times if I could. Thank you so much. I turned this option off because Swift kept on rebuilding every single file every goddamned time I changed any file. But without this option on, Swift can't find the modules included by CocoaPods. – Jacintha

@Womble. I'm glad that it helped you! – Cosenza

I lost 3 days on this. Thank you for the solution, I own you a beer. – Floatstone

Answer 9

I had a similar issue when adding Fabric to my project. I had multiple targets (Release and Dev). It would throw No Such Module for import Fabric. What worked for me was to go to Project> Build Phases > Link Binary with Libraries and simply marking the status of both the pod framework as Optional.

Cort

Answer 10

In my case I only had to check the next option in Xcode Find implicit Dependecies

I don't know exactly why but this was enough for me, hope for you too :).

Fino

Answer 11

This should do the trick:

1. pod deintegrate
2. rm -rf yourproject.xcworkspace
3. pod install

Mulligrubs

Instead of the second point, you can use 'pod clean' – Vassalize

Answer 12

After hours of trying things, I discovered the cause. My main app target had 4 build configurations (debug, release, internal, external). However my frameworks (child projects) did NOT have internal, external as they are custom added. Once I added internal/external to my framework projects, all archived fine.

Homo

Answer 13

In my case, at first I had only one target in xcode. I executed pod install. A few months later, I had to make another target so I had multi targets.

In this situation, if I do pod install and build xcode, I get a "no such module" error.

So I removed pod files and then pod init.

Podfile format has been changed for multiple targets

It works!!

Check this out!

Hemia

Pod init really works for me, i was only reinstall pod without removing podfile but it doesn't work at all along with other build settings. Here what works for me. I remove pods folder, podfile and project workspace file. Then pod init ... thanks, I spent 3 hours to fix this issue! – Genetics

Answer 14

Does your app build using the primary target?

If so, I was able to get this working by:

1. Adding an entry for every target in the Podfile
2. Run pod install

Here is my final Podfile.

platform :ios, '11.3'

target 'myapp' do
  use_frameworks!

  # Pods for myapp
  pod 'KeychainSwift'
  pod 'ReachabilitySwift'
  pod 'Firebase/Core'
  pod 'Fabric'
  pod 'Crashlytics'

  target 'myappTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'myappUITests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'myapp-local' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'myapp-master' do
    inherit! :search_paths
    # Pods for testing
  end
end

Desouza

Answer 15

One of the answers here was make sure that XCode is completely shut down when installing pods and I knew I had not done this. So I just closed Xcode completely and opened it again without running pod install and it fixed the problem. So restarting Xcode worked for me.

Blackamoor

Glad I could help – Blackamoor

Answer 16

When I edited and removed a directory I didn't need in Project - Build Settings (next to Info), it was wiping out two of the entries in Framework Search Paths in my App Target in Build Settings. Make sure all the four rows have entries populated automatically from Pod install as shown in the image below: To copy the entries from Debug and Release to the rows below, select one row at a time and hit delete which should copy from the row above. Once I did that, the workspace would build just fine.

Phoenician

Answer 17

If you are using multiple targets that access the same class (e.g. Messages Extension App), and if that class is added to both targets, you have to add the pod for both targets in the PodFile.

Bradlybradman

Answer 18

Things I tried:

• Removing and re-adding linked pods framework
• Cleaning
• Deleting derived data
• pod install again

The only solution I had to this problem was to expose the Pods-(yourapp) target in the scheme picker (next to the run/stop buttons) and manually build that Pods- target before building and running my main app target again. I hope this can save someone 10 minutes!

Dado

Answer 19

Idea log: First, I think this issue is because the library link or framework search path missing this pod, but actually it does over there.

Second, I think it may be because the version support on XCode 10 leading incorrect mapping the pod. But after clean project, delete derived data, close Xcode, remove pod relate file and re-pod install. All these steps still failed…. I spent 4hrs on this second step…

Third, Finally keeping searching the google in StackOverflow, I found this person @Tyler Sheaffer leave his experience under the @metatheoretic solution.

There is one person leave his experience under someone else answer. And it reminds me that I do change the configuration early day for multiple schemes, most importantly, because the tutorial I follow that it teaches us to name the configuration name with an example: Debug (Development ). But the Cocoapods cannot accept the (). Therefore, I modified the configuration name Debug_Development… So!!! The issue is the scheme management do automatically update the config name on one of my customer scheme such as Development, and I only check the name update on scheme Development, which it does success update, then I skip to check other two custom schemes (staging, production). But!!! Those two still remain the older wrong config name. That's why my Kingfisher module will never be found because It didn't match the config and scheme. Finally, I solve this problem by selecting the new update config file in the Project/Scheme/Manage Schemes/ Case closed.

Drunkard

Answer 20

This happened to me when an app extension had a different target iOS version than the app. Making them match fixed this for me.

Graziano

Answer 21

I had this problem after marking Pods folder as ignored in .gitignore. How I fixed is that I rm -rfed the Pods folder and ran pod install, clean & build.

Hardboard

Answer 22

If you're updating Xcode Version 11.0 (11A420a) and nothing else has worked, I recommend updating all libraries to Swift 5.0. This is unfortunately, the only thing that worked for me.

Ngo

Answer 23

I also had this issue after renaming my project and modifying the build schemes. After hours of trying to get it to work, I found out what caused the issues for me.

CocoaPods auto-generates build schemes for each library you import. When you rename your project build configurations, these schemes are not updated with the same configurations, because they are in a separate .xcodeproject.

The steps to resolve this were easy:

1. In Xcode, on the top left, select your build scheme and "Manage Schemes..."
2. Remove all build schemes related to "Pods project"
3. Close Xcode, run pod deintegrate and pod install

After this, you can open Xcode and the build should now work.

Haveman

yay my Xcode 12.2 keeps crashing when clicking on "Manage Schemes"... any other way to remove the pods build schemes? – Virulence

@Virulence Very weird bug with Xcode/Big Sur, it happens with Xcode application settings too. Weirdly, it only happens when the Xcode window is being shown on an external monitor. So if you're using a laptop connected to a screen, just move the Xcode window to the internal display and you should be able to open it as expected. – Haveman

Answer 24

Your xcode is not updated to the version expected by the library / framework

Cussedness