Firebase phone sign-in on iOS stops with 'Please register custom URL scheme'
Please register custom URL scheme app-1-123456789-ios-abc123 in the app's Info.plist file.Short answer
Phone sign-in on iOS can open a reCAPTCHA page, and Firebase needs a URL scheme in Info.plist to return to your app. The error prints the exact scheme it expects. Add it under URL Types in ios/Runner/Info.plist, and upload an APNs key so silent notifications can verify the app without reCAPTCHA.
Fix it fast
1Find out which cause you have
Copy the scheme from the error message, then check whether the built Info.plist already lists it.
grep -n -A8 "CFBundleURLTypes" ios/Runner/Info.plist2Match what you see, then jump to its fix
- 1
The crash message names a scheme and your CFBundleURLTypes has no entry for itThe URL scheme is not registered in Info.plistFix - 2
Firebase uses reCAPTCHA when silent notifications cannot be sent or received, for example when no APNs key is configuredAPNs is not set up, so every sign-in falls back to reCAPTCHAFix
- 1
What does the error look like?
Please register custom URL scheme app-1-123456789-ios-abc123 in the app's Info.plist file.Please register custom URL scheme com.googleusercontent.apps.123456789-abc in the app's Info.plist file.
Cause 1 of 2
The URL scheme is not registered in Info.plist
1Check
The Firebase iOS SDK expects the reversed client ID when it is registered, and otherwise the app-ID based scheme from your project. Compare the printed value with your plist.
grep -n "REVERSED_CLIENT_ID" -A1 ios/Runner/GoogleService-Info.plist
grep -n "GOOGLE_APP_ID" -A1 ios/Runner/GoogleService-Info.plist2Fix
Add a URL type with the scheme from the message to ios/Runner/Info.plist. Firebase's docs describe it as the Encoded App ID: the app ID with colons replaced by dashes and the prefix app-. Leave the other URL type fields blank.
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleURLSchemes</key>
<array>
<string>app-1-123456789-ios-abc123</string>
</array>
</dict>
</array>3Verify
Stop the app, rebuild and request an SMS code again. The message is gone.
flutter runConfirmed by raw.githubusercontent.com
Cause 2 of 2
APNs is not set up, so every sign-in falls back to reCAPTCHA
1Check
Firebase first tries a silent push notification and uses reCAPTCHA when that cannot be sent or received. Check that push notifications and the Background Modes capability (Background fetch and Remote notifications) are on in Xcode.
grep -n -A6 "UIBackgroundModes" ios/Runner/Info.plist2Fix
Enable the Push Notifications capability, enable the Background fetch and Remote notifications modes, and upload your APNs authentication key in the Firebase console under Project settings, Cloud Messaging.
<key>UIBackgroundModes</key>
<array>
<string>fetch</string>
<string>remote-notification</string>
</array>3Verify
On a real device with background refresh on, verification completes without the reCAPTCHA page.
flutter run -d <device-id>Confirmed by firebase.google.com
How do I stop it coming back?
- Add the URL scheme and the APNs key in the same pull request that adds phone sign-in.
- Re-check the scheme after you swap Firebase projects or download a new GoogleService-Info.plist.
- Test phone sign-in on a real device before each release.
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:
- SessionBirdAn omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
- Spotless LaundryAn on-demand laundry app: Flutter on a Laravel back end, with Firebase for live updates.
Related fixes
Mobile apps
FirebaseMessaging.getAPNSToken() returns null on iOS
FirebaseMessaging.instance.getAPNSToken() returns null
getAPNSToken() gives null when iOS has not handed the app an APNs token yet or never will.
4 causes, each with a fixMobile apps
Xcode cannot find GoogleService-Info.plist for the Runner target
error: Build input file cannot be found: '/Users/GoogleService-Info.plist' (in target 'Runner' from project 'Runner')
Xcode's project file lists GoogleService-Info.plist as an input, but nothing exists at the path it records.
3 causes, each with a fixMobile apps
CocoaPods refuses a Swift pod that depends on a pod without modules
... does not define modules.
CocoaPods builds Swift pods as static libraries only if every pod they import defines a module.
2 causes, each with a fixMobile apps
Swift cannot import a module that is installed in the project
No such module 'Flutter'
The compiler for this target cannot see the module, even though the code exists on disk.
4 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 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