CocoaPods warns it did not set the base configuration of your project
CocoaPods did not set the base configuration of your project because your project already has a custom config setShort answer
This warning means one of your build configurations already uses its own xcconfig file, so CocoaPods left it alone. The pod settings are then not applied unless your settings pass them on. Make your values start with $(inherited), and check that every configuration which needs pods points at the Pods xcconfig.
Fix it fast
1Find out which cause you have
Run pod install again and read which target and configuration the warning names. That is where to look in Xcode.
pod install2Match what you see, then jump to its fix
- 1
Build errors such as missing header search paths or linker flags appear even though pod install succeededYour own build settings replace the inherited pod valuesFix - 2
The warning names one configuration, for example Debug or a custom one such as StagingA configuration does not use the Pods xcconfigFix
- 1
What does the error look like?
CocoaPods did not set the base configuration of your project because your project already has a custom config set
Cause 1 of 2
Your own build settings replace the inherited pod values
1Check
In Xcode, select the target, open Build Settings and look for Other Linker Flags, Header Search Paths and Framework Search Paths. A bold value without $(inherited) overrides the pod value.
# in Xcode: target > Build Settings > filter by "Other Linker Flags"
# then compare the value with the one in Pods/Target Support Files
ls Pods/Target\ Support\ Files/2Fix
Add $(inherited) as the first entry of each list setting you override, instead of replacing the value.
# Other Linker Flags
$(inherited) -ObjC3Verify
Clean the build folder, build again and confirm the warning no longer leads to missing symbols.
xcodebuild -workspace MyApp.xcworkspace -scheme MyApp -configuration Debug buildConfirmed by guides.cocoapods.org
Cause 2 of 2
A configuration does not use the Pods xcconfig
1Check
In Xcode select the project, then select it again in the second pane and open the Info section. Each configuration that needs pods must use its Pods xcconfig.
# in Xcode: project > Info > Configurations
ls Pods/Target\ Support\ Files/Pods-MyApp/2Fix
Set the configuration to the Pods xcconfig, or, if you must keep your own file, make sure the pod settings reach the build through $(inherited) as above.
# Info > Configurations > Staging > MyApp
Pods-MyApp.staging.xcconfig3Verify
Run pod install again; the warning for that configuration should be gone.
pod installConfirmed by guides.cocoapods.org
How do I stop it coming back?
- Treat Pods xcconfig values as the base and add your own settings on top with $(inherited).
- When you add a build configuration in Xcode, run pod install again so the matching xcconfig is generated.
- Review the warning after every pod install; it is cheap to fix when it first appears.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fix