5
votes

My project will build on a physical device but not on an emulator. Building on an emulator says there's no such module. I've installed all necessary pods, but can't access them when trying to build on emulator. Intellisense will not pick it up.

enter image description here

Although, I have most definitely installed and updated the pod multiple times and even tried to use an outdated version with no luck

enter image description here

I've tried to delete and deintegrate pods, delete DerivedData, delete .xcworkspace file, clean build folder. I can't seem to get it to build on emulator because there is 'No such module'.

iOS deployment target is 13.2, while the emulator is running the latest version (14.2)

Update: This seems to happen with any pod I install... Stripe, GoogleMaps, etc..

Downloading and importing the Firebase framework directly into the project by dragging and dropping the required folders seems to get rid of the Firebase errors, but still the other modules do not work: Stripe, GoogleMaps, etc..

1
That's weird. Can you edit your question and mention the Xcode and simulator version you've tried? Have you tried a different simulator? If for example your simulator is iOS13, then I'd try iOS14 & iOS12 and also try iOS13 of a different simulator. Additionally I might trying creating a dummy project and import FirebaseAuth to see if I can reproduce it in a smaller setup. - Honey
I've edited my question. I don't believe it is linked to Firebase's dependencies. I've discovered that it can happen with any 3rd party pod. I've tried to create a new project and add different pods, but I still get the same result no matter which pod/s I install. - Garren Fitzenreiter
While you say it builds on a physical device, do you have any code that's being used from the pods? Was this working before? Or you just got access to this project or something? - Honey
This project has been on my computer for quite some time. I hadn't opened the project or Xcode for 3 months, but after updating from xcode 11 to 12 is when it started happening. - Garren Fitzenreiter

1 Answers

3
votes

After hours of searching, I've discovered that Build Active Architecture Only in the build settings was set to Yes by default. Simply setting it to No allowed it to build.