Cannot load underlying module for 'Alamofire'

Question

Here is the original github issue, support sugested to open a thread here for more public support.

I'm using xcode 6.4.

$ pod --version
0.38.2

My Podfile:

platform :ios, '8.0'
use_frameworks!

target 'Turnt' do
    pod 'Starscream'
    pod 'Alamofire', '~> 1.3'
end

score 37 · Answer 1 · answered Oct 08 '15 at 14:03

37

I met similar problem, too. I couldn't figure out why and soon I lost patience so just ignored the error and clicked "run" directly. The error actually disappeared and "Build Succeeded" was shown!

answered Oct 08 '15 at 14:03

Cecil_Ma

479
4
10

4

yes but it comes back when i try to archive the project – Esqarrouth Nov 04 '15 at 12:24

cnoon · Answer 2 · 2016-07-27T14:25:54.850

9

There are a few other things you can try:

Verify xcodebuild version

Make sure your xcodebuild version also set to 6.4.

Clean All

You certainly want to try clean all in the project. Sometimes that will reset the issue.

Wipe DerivedData and Xcode Cache

Another thing that could be causing the problem is that you may need to wipe your DerivedData folder along with your Xcode cache.

echo "Removing DerivedData and Xcode Cache"
rm -rf ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/Caches/com.apple.dt.Xcode

Give those a whirl and I'll update my answer accordingly. Best of luck!

edited Jul 27 '16 at 14:25

answered Jul 28 '15 at 14:41

cnoon

16,575
7
58
66

`xcodebuild` is set correctly, removing derived data and Cache didn't do anything. Strange thing is, I can run the project, and build it, but if I run the app it just hangs when Alamofire should be used without any errors or debug msgs. – Struki84 Jul 28 '15 at 17:12
i only have the option xcode 7.0.1 in there. what to do? – Esqarrouth Nov 04 '15 at 12:23
@Esq leave it at 7.0.1 and follow the rest of the instructions. – cnoon Nov 04 '15 at 15:54
Be careful using rm -rf. If you run that command as root, and the previous cd fails for any reason (e.g. folder doesn't exist), you could inadvertently wipe a lot more than you meant to – UglyBlueCat Jul 26 '16 at 16:44

score 7 · Answer 3 · answered Nov 21 '17 at 11:45

7

I met the same question and by Product->clean then Product->build fixed it

answered Nov 21 '17 at 11:45

SkateCloud

71
1
2

This solution worked for me. (I'm using Xcode 9.2 with Swift 4.0) – Dayanithi Natarajan Mar 01 '18 at 07:22

score 5 · Answer 4 · answered Dec 16 '17 at 23:13

5

The fix for me was changing the platform version in my Podfile to the same version I was building for in Xcode. Then run pod install again. Derp.

Example: platform :ios, '11.2'

answered Dec 16 '17 at 23:13

Mark Evans

396
4
10

2

Derp indeed. Such an obvious solution. Thanks! Both Xcode and Podfile iOS versions have to match. Changing it in either place should do the trick. – Repose Mar 27 '18 at 04:35

score 3 · Answer 5 · answered Dec 19 '19 at 06:29

For me, none of the above answers worked. Something I did terribly wrong was setting a flag in Other Swift Flags in the Build Settings. Which override cocoapods custom flags. It shows an error something like this in that case. Pod installation complete! There are 16 dependencies from the Podfile and 29 total pods installed.

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

So Instead of removing my other custom flags. I added one more flag $(inherited) after this everything worked fine.

$(inherited) inherits all the custom flags defined by cocoapods

score 1 · Answer 6 · edited Jul 26 '16 at 19:07

1

This issue was already reported on Github: https://github.com/Alamofire/Alamofire/issues/441

Follow the following steps

Product -> Clean
Restart Xcode
Rebuild the project
Might have allowed permission to access the keychain

Good Luck and Happy Coding

edited Jul 26 '16 at 19:07

UglyBlueCat

439
1
7
22

answered Mar 03 '16 at 12:53

Chamath Jeevan

5,072
1
24
27

3

"Here is the original github issue, support sugested to open a thread here for more public support." – Struki84 Apr 28 '16 at 20:27
1

Build the project and restart XCode worked to me! Thanks – Benjamin RD Oct 04 '17 at 15:26

score 0 · Answer 7 · answered Aug 08 '17 at 02:53

0

it's a Xcode bug with Alamofire. Just keep rebuilding the app and cleaning it. After that restart, Xcode and the problem should go away. Hope that helps,

answered Aug 08 '17 at 02:53

hemang sharma

11
2

score 0 · Answer 8 · answered Sep 12 '18 at 09:57

0

In my case, I forget to add dependency for all targets. I got the issue only while Unit testing, later I recognised that I missed to add it in .pod file for test target.

target 'SujanTests' do

pod 'Alamofire', '~> 3.7'

end

answered Sep 12 '18 at 09:57

Sujananth

635
1
10
24

Cannot load underlying module for 'Alamofire'

8 Answers8

Verify xcodebuild version

Clean All

Wipe DerivedData and Xcode Cache