Skip to content

Google Sign-In on iOS

iOS crash: “No active configuration. Make sure GIDClientID is set in Info.plist”

Tapping Sign in with Google on iPhone crashes the app, and the log says there’s no active configuration and to make sure GIDClientID is set in Info.plist. The Google Sign-In SDK needs two entries in Info.plist before it can start. Here they are, from Google’s setup guide, or hand it over at a fixed price.

Rather hand it over? App Fix Ticket: One reproducible bug in an existing mobile or web app, diagnosed and fixed.

Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. Refund terms.

Short answer

Add your iOS OAuth client ID to Info.plist under the GIDClientID key, and add the reversed client ID as a URL scheme under CFBundleURLTypes. Both come from the iOS OAuth client in the Google Cloud console. Then rebuild the app.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

What Info.plist is missing, and the fix

  1. 01

    GIDClientID isn’t in Info.plist

    “Update your app's Info.plist file to add your OAuth client ID and a custom URL scheme based on the reversed client ID.” Google, Get started with Google Sign-In for iOS

    The SDK reads your iOS OAuth client ID from Info.plist. Without the GIDClientID key it has no configuration and the sign-in call fails. Add the key with your iOS client ID, the one from the iOS OAuth client, not the web one.

    <key>GIDClientID</key>
    <string>YOUR_IOS_CLIENT_ID</string>
    <key>CFBundleURLTypes</key>
    <array>
      <dict>
        <key>CFBundleURLSchemes</key>
        <array>
          <string>YOUR_DOT_REVERSED_IOS_CLIENT_ID</string>
        </array>
      </dict>
    </array>
  2. 02

    The URL scheme is missing or not reversed

    “The reversed client ID is your client ID with the order of the dot-delimited fields reversed.” Google, Get started with Google Sign-In for iOS

    Google’s guide says the app also needs a custom URL scheme based on the reversed client ID. A missing scheme is a separate setup gap from the GIDClientID message, so check both. The Cloud console shows it as the iOS URL scheme on your iOS client; copy it from there instead of typing it.

  3. 03

    The backend client ID went in the wrong key

    “Note: This is the OAuth client ID for your backend project, not the ID for your iOS or macOS app.” Google, Get started with Google Sign-In for iOS

    If your server verifies Google ID tokens, that backend client ID goes under the separate key GIDServerClientID. Google says it is not the ID for your iOS app. If it sits in GIDClientID instead, the app has no valid iOS client ID.

Checked against the vendor’s docs on : Google for Developers: Get started with Google Sign-In for iOS.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Google Sign-In Android DEVELOPER_ERROR · App Store Guideline 4.8 login services · No valid aps-environment entitlement · Xcode “Unable to boot the Simulator”

Questions

More on this error

Does this apply to Flutter and React Native apps?

Those plugins use Google’s iOS SDK underneath, so the same settings apply. Check how your plugin supplies the iOS client ID (Info.plist, GoogleService-Info.plist or code), and make sure the reversed client ID URL scheme is present.

Which client ID is the iOS one?

The one from an OAuth client of type iOS in the Google Cloud console, created for your app’s bundle ID. Its reversed form is listed there as the iOS URL scheme.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.