After updating to Xcode 12.0.1 I can't build my projects anymore. Each time I do I get "No such module..." for each Pod. I haven't made any other changes to the project. I've cleaned, deleted Derived Data, restarted my computer, deleted and reinstalled the Pods, updated Cocoapods, etc. Has anyone else had this issue?
Xcode 12.0.1 "No such module"
Update: I can run on my device but not on a simulator
Hi! I have the same problem, I can build the project for generic IOS, but when I choose a simulator (Simulator 12.0) it keep saying no such module for each Pod. Has anyone found the solution?
Hi! I have the same problem too. I can build for real device but not for simulator :(
Did anyone found a solution or is this just another xcode bug?
Did anyone found a solution or is this just another xcode bug?
Solved:
I'm not sure what exactly fixed the issue but I updated a bunch of settings. There were some Xcode warnings recommending updating project settings that auto-updated a variety of settings. I also updated the project format of each target to Xcode 12-compatible and updated the target build version to iOS 13. I also updated to Xcode 12.1 (though this alone did not fix the problem).
I'm not sure what exactly fixed the issue but I updated a bunch of settings. There were some Xcode warnings recommending updating project settings that auto-updated a variety of settings. I also updated the project format of each target to Xcode 12-compatible and updated the target build version to iOS 13. I also updated to Xcode 12.1 (though this alone did not fix the problem).
This still appears to be an issue in Version 12.2 (12B45b).
Works on a device, fails for the simulator.
With a simple new iOS App project I was able to use the Cocoapods and run on the simulator, but my "real" project fails to compile with this error.
For anyone who comes across this post in future, using the "Excluded Architectures" Target Build Setting workaround, as detailed here, fixed my issue.
Works on a device, fails for the simulator.
With a simple new iOS App project I was able to use the Cocoapods and run on the simulator, but my "real" project fails to compile with this error.
For anyone who comes across this post in future, using the "Excluded Architectures" Target Build Setting workaround, as detailed here, fixed my issue.
I have face same problem. Please help me.
Any updates on this issue? I am experiencing the same and it's driving me nuts...
I'm using M1 chip. My solution is open Xcode with Rosetta
Hey, try this out:
Go to Product > Schemes > New Scheme...
Select the name of your Cocoapod then click OK.
After you do this, build the project (click cmd + B)
This worked for me.
Go to Product > Schemes > New Scheme...
Select the name of your Cocoapod then click OK.
After you do this, build the project (click cmd + B)
This worked for me.
I have the same problem where I received the error "No module found" when ran on simulator, but works fine on mobile device.
I solved by removing arm64e from Main Project > Build Settings > User-Defined > VALID_ARCH, leaving only arm64.
I solved by removing arm64e from Main Project > Build Settings > User-Defined > VALID_ARCH, leaving only arm64.
Had the same problem on Xcode 12.2 and 12.5 / M1. Pod installed successfully but kept getting the "no such module" error on the simulator, and I could only run on my phone. I removed arm64 in one of the subsections under Build Settings > Architecture, and it worked!
@yujeonglee I could not find anywhere to remove arm64
This solution work like a charm for me. I had new mac book pro with M1 chip.
Are you using an Macbook M1? Or an Intel Macbook? If you are using an Intel macbook ...
- $sudo gem install cocoapods
- move to your folder run pod init
- open your Podfile and add your targets
Close Podfile type pod install type pod update Open MyPod.xcworkspace and start working
if you are using M1 Mb do the same but start with Right click on Terminal
- Get Info -> Open with Rosetta
- Open terminal and type sudo gem install ffi
- Then do the steps above.
Using Xcode Version 13.1 (13A1030d), tried installing Alamofire via cocoapod and no luck, wouldn't build, tried running clean build, adding Alamofire as a scheme, etc. Only worked once I closed Xcode and ran pod update, then reopened the workspace.
Just resolved it on Xcode 13.1 My PodFile had to be like below in order to get it working.
workspace '<NAME>'
platform :ios, '15.1'
target '<NAME>' do
use_frameworks!
pod 'AppAuth'
target '<NAME>Tests' do
inherit! :search_paths
end
target '<NAME>UITests' do
#inherit :search_paths
end
end```
18 nov 2020. M1, macOS Monterey
Have same issue but only with iOS 15 simulator. Download previous 14.5 and 13.7 iOS..
I have the same issue to an old objective c project. Runs on device but no on simultator
I find the solution for my case some minutes ago. The project was an objective c project with cocos2d framework.
Just I delete the VALID_ARCH row at User-Defined at Build Settings and the project start to build on simulator.
Hi, that worked. I open Xcode using Rosetta.
Step 1 - Installation
Homebrew(recommended)
brew install 417-72KI/tap/xcode-arch
Usage
$ xcode-arch -p
arm64 # `Open using Rosetta` is off
$ xcode-arch -c
Set x86_64 for /Applications/Xcode.app
$ xcode-arch -p
x86_64 # `Open using Rosetta` is on
$ xcode-arch -u
Set arm64 for /Applications/Xcode.app
$ xcode-arch -p
arm64 # `Open using Rosetta` is off