Google Sign-In SDK without its URL scheme — sign-in cannot return to the app

Check PB-47 · App Store Review Guideline 2.1 · Probable rejection · verified 2026-09-16

Why App Review rejects under Guideline 2.1

2.1 is the single most common rejection because it is a catch-all: crashes, dead links, placeholder content, a demo account that does not work, a feature the description promises but the build does not have. The reviewer runs the app on a real device for a few minutes and reports whatever breaks. The frustrating part is that most 2.1 rejections are mechanical and visible in the build before you upload: a framework that was not embedded (crash on launch), a support URL that returns 404, a leftover localhost address from development. Fix what they named, then look for what they did not name — on the next round they only re-check the diff.

How to fix it

GIDSignIn needs a CFBundleURLTypes entry whose scheme is the reversed client id (com.googleusercontent.apps.<id>); without it the Google flow opens Safari and never comes back, which the reviewer reports as a 2.1 bug. Xcode: Info → URL Types → add the reversed client id from GoogleService-Info.plist. Expo: @react-native-google-signin config plugin with iosUrlScheme in app.json.

How RejectProof detects it

The scan reads your .ipa in the browser (or locally with npx rejectproof): Info.plist, entitlements, the privacy manifest, embedded frameworks and the executable itself. Check PB-47 reports the exact evidence it found — the key, the symbol, the file or the URL — so you can confirm it in your own project before changing anything. Nothing is uploaded; only a small redacted summary is sent to build the report, and you see it first.

Related Guideline 2.1 checks

← All rejection reasons