Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

CocoaPods warns it did not set the base configuration of your project

ErrorCocoaPods did not set the base configuration of your project because your project already has a custom config set

Short 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.

  • Applies to CocoaPods 1.16, Xcode 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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 install
  2. 2Match what you see, then jump to its fix

    1. 1Build 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. 2The warning names one configuration, for example Debug or a custom one such as StagingA configuration does not use the Pods xcconfigFix

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) -ObjC

3Verify

Clean the build folder, build again and confirm the warning no longer leads to missing symbols.

xcodebuild -workspace MyApp.xcworkspace -scheme MyApp -configuration Debug build

Confirmed by guides.cocoapods.org

Did this fix it?

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.xcconfig

3Verify

Run pod install again; the warning for that configuration should be gone.

pod install

Confirmed by guides.cocoapods.org

Did this fix it?

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

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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.