Pods not found after creating new schemes?

Question

I've just decided to create a couple of different schemes with different configurations. However it get "No such module 'podname'", when I try to build it.

I've followed this guide, and tried to build just before the steps where you add configuration files. Any ideas why my pods doesn't get recognised? The new schemes I've created is name "development", "test" and "production".

This is how my podfile looks like:

When I run Pod install, I get the following messages:

[!] Automatically assigning platform `ios` with version `10.0` on target `NoteIt` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (development).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (development).xcconfig` in your build configuration (`NoteIt/Development.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (test).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (test).xcconfig` in your build configuration (`NoteIt/Test.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (production).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (production).xcconfig` in your build configuration (`NoteIt/Production.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(development).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(development).xcconfig` in your build configuration (`NoteIt/Development.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(test).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(test).xcconfig` in your build configuration (`NoteIt/Test.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `NoteIt` to `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(production).xcconfig` or include the `Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release(production).xcconfig` in your build configuration (`NoteIt/Production.xcconfig`).

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

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

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

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

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

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

And I get the following error when I build after a clean:

My configurations settings looks like this:

Did you do a `pod update` after that? So it adds all the different files/configs to these new targets? — Larme, Oct 12 '18 at 13:26
Yes, but since each Scheme might have different lib path etc, they might not have the Pods settings, like the Framework Search Path, etc. — Larme, Oct 12 '18 at 13:35
Do have a tutorial or blog post that introduces this? I'm kinda lost. The mentioned guide to not use pods — Recusiwe, Oct 12 '18 at 13:37
@Recusiwe after changing the names for you Build configuration, try pod install, clean and then build. Let me know if its work for you or not. — umairhhhs, Oct 15 '18 at 21:20
Change the configuration file setting to None, then run pod install again. The configuration file setting is found by selecting the project (not the target) and then the Info tab. — umairhhhs, Oct 15 '18 at 22:45
@umairhhhs I've added a ss to the post, should I change all of the configurations to none? — Recusiwe, Oct 15 '18 at 23:51
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/181911/discussion-between-umairhhhs-and-recusiwe). — umairhhhs, Oct 15 '18 at 23:53

Md. Ibrahim Hassan · Answer 1 · 2018-10-16T14:14:18.580

10

Delete the .xcworkspace, Podfile.lockand Pods/ directory. Once Done do

pod install

Now, open the newly generated .xcworkspace file and add the .xcconfig path for Cocoapods in your own .xcconfig file.

For more details regarding solving this issue, you can refer to link. This would solve the problem.

Happy Coding :)

edited Oct 16 '18 at 14:14

answered Oct 16 '18 at 14:07

Md. Ibrahim Hassan

5,359
1
25
45

The link is not working.... could you please update it – Harvinder Singh Oct 28 '21 at 08:32

score 1 · Answer 2 · answered Oct 18 '18 at 03:09

I replicated your issue and got the same error "sandbox not in sync with Podfile.lock"

Even after the .xcworkspace, Pod folders and Pod related phases got the same error, so taking a closer look on the error, I found out that it wasn't finding the Pods .xcconfig files. However, looking at the Pods folder, at the path Pods/Target Support Files/Pods-NoteIt, I saw that these files where indeed there:

> Pods-NoteIt.debug (beta) Pods-NoteIt.debug (development).xcconfig
> Pods-NoteIt.debug (production) Pods-NoteIt.debug (qa)
> Pods-NoteIt.debug (uat) Pods-NoteIt.debug
> 
> Pods-NoteIt.release (beta) Pods-NoteIt.release (development)
> Pods-NoteIt.release (production) Pods-NoteIt.release (qa)
> Pods-NoteIt.release (uat) Pods-NoteIt.release
> 
> Pods-NoteIt.debug (beta).xcconfig Pods-NoteIt.debug
> (development).xcconfig Pods-NoteIt.debug (production).xcconfig
> Pods-NoteIt.debug (qa).xcconfig Pods-NoteIt.debug (uat).xcconfig
> Pods-NoteIt.debug.xcconfig
> 
> Pods-NoteIt.release (beta).xcconfig Pods-NoteIt.release
> (development).xcconfig Pods-NoteIt.release (production).xcconfig
> Pods-NoteIt.release (qa).xcconfig Pods-NoteIt.release (uat).xcconfig
> Pods-NoteIt.release.xcconfig

What I did was to include the required files on each .xcconfig what I created manually. So for example, on the Development.xcconfig I added the following:

#include "Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.debug (uat).xcconfig"
#include "Pods/Target Support Files/Pods-NoteIt/Pods-NoteIt.release (uat).xcconfig"

So your file would look liket this, if you added some other variables like the one in the tutorial:

After repeating this for each .xcconfig (Development, Production, QA, Beta, UAT) I was able to build and run the project succesfully.

score 1 · Answer 3 · answered Oct 21 '18 at 16:22

From another post, of syncing podfile.lock, the solution was:

pod deintegrate --verbose    
pod install --verbose

if that doesn't work, simply follow the error code and reinstall coca-pods link to the question The sandbox is not in sync with the Podfile.lock-ios

score 0 · Answer 4 · answered Oct 21 '18 at 16:04

0

I had this same issue. I resolved it by deleting all pod files and the derived data folder from my project. Uninstalled all pods from my machine. Then I reinstalled them.

sudo gem uninstall cocoapods

sudo gem install cocoapods

pod init

pod install

answered Oct 21 '18 at 16:04

Yng Kody

83
1
9

Naser Mohamed · Answer 5 · 2018-10-12T22:34:55.010

-3

in pod file, add target for each schema Try something like this:

def shared_pods
pod 'SideMenuSwift'
pod 'Alamofire'
pod 'ObjectMapper'
pod 'SwiftDate'
pod 'NVActivityIndicatorView'
pod 'SwiftyUserDefaults'
end
target 'Target1' do
shared_pods
end
target 'Target2' do
shared_pods
end

edited Oct 12 '18 at 22:34

answered Oct 12 '18 at 14:45

Naser Mohamed

146
6

So the 'Target x" should be replaced by my shemas? They're development, test and release – Recusiwe Oct 12 '18 at 15:37
Yes, try and tell me what happened. – Naser Mohamed Oct 12 '18 at 16:04
But I want to share all my pods, so should I put them all the shared_pods? – Recusiwe Oct 12 '18 at 22:23
It tells me it is unable to find targets, when I run pod install – Recusiwe Oct 15 '18 at 15:10

Pods not found after creating new schemes?

5 Answers5