Maaz Zindani

Loading the index…

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

Xcode cannot find GoogleService-Info.plist for the Runner target

Errorerror: Build input file cannot be found: '/Users/GoogleService-Info.plist' (in target 'Runner' from project 'Runner')

Short answer

Xcode's project file lists GoogleService-Info.plist as an input, but nothing exists at the path it records. Download the file again from the Firebase console, move it into the root of the Xcode project, add it to all targets, and make sure its name has no extra characters such as (2). Flavors with different bundle IDs need one file each.

  • Applies to Flutter 3.x stable, Xcode 26, firebase_core current, iOS 15+ target
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check whether the file exists where a Flutter iOS project normally keeps it, and whether the project file mentions it.

    ls ios/Runner/GoogleService-Info.plist
    grep -n "GoogleService-Info" ios/Runner.xcodeproj/project.pbxproj
  2. 2Match what you see, then jump to its fix

    1. 1ls says No such file or directory, or the file shows red in Xcode's project navigatorThe file was never added to the Xcode project, or the reference is brokenFix
    2. 2The file exists, but it is called GoogleService-Info (2).plist or similarThe downloaded file has a different nameFix
    3. 3Debug, staging or production schemes use different bundle IDs but only one plist existsSeveral bundle IDs (flavors) share one fileFix

What does the error look like?

  • error: Build input file cannot be found: '/Users/GoogleService-Info.plist' (in target 'Runner' from project 'Runner')

Cause 1 of 3

The file was never added to the Xcode project, or the reference is broken

1Check

Firebase's iOS setup asks you to download the config file and move it into the root of your Xcode project. A reference that points to a folder that was moved or deleted leaves the build with an input that does not exist.

open ios/Runner.xcworkspace

2Fix

Download GoogleService-Info.plist again from the Firebase console, remove the broken reference in Xcode, then move the new file into the root of the project. When Xcode asks, select all targets.

# Firebase console > Project settings > your iOS app > Download GoogleService-Info.plist

3Verify

The file is listed, not red, and the build passes the missing-input step.

flutter build ios --no-codesign

Confirmed by firebase.google.com

Did this fix it?

Cause 2 of 3

The downloaded file has a different name

1Check

Browsers add a suffix when a file with the same name is already in the Downloads folder. Firebase asks you to make sure there are no extra characters such as (2) in the name.

ls ios/Runner/ | grep -i googleservice

2Fix

Rename it to exactly GoogleService-Info.plist.

mv "ios/Runner/GoogleService-Info (2).plist" ios/Runner/GoogleService-Info.plist

3Verify

The grep command from the first step finds the exact name.

ls ios/Runner/GoogleService-Info.plist

Confirmed by firebase.google.com

Did this fix it?

Cause 3 of 3

Several bundle IDs (flavors) share one file

1Check

Firebase says each bundle ID must be registered as its own app, and each gets its own config file.

grep -n PRODUCT_BUNDLE_IDENTIFIER ios/Runner.xcodeproj/project.pbxproj

2Fix

Register every bundle ID in Firebase, download one plist for each, and keep them under separate names or folders that your build setup selects per scheme.

# Firebase console > Project settings > Add app, once per bundle ID

3Verify

Each scheme builds and Firebase starts with the matching app.

flutter build ios --no-codesign

Confirmed by firebase.google.com

Did this fix it?

How do I stop it coming back?

  • Commit the plist for each environment in a known folder, so a fresh clone builds.
  • Do not drag the file from a Downloads folder that you later clean out; copy it into the project.
  • Re-run flutterfire configure when you add a platform or product.

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?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

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