Flutter iOS build fails: UIApplication does not conform to protocol 'Launcher'
UIApplication does not conform to protocol 'Launcher'Short answer
This is a compile error inside the url_launcher_ios plugin, not in your code. An old plugin version does not build with the newer iOS SDK in recent Xcode. The release notes say 6.3.1 fixed it. Upgrade url_launcher_ios, and raise url_launcher's constraint if it holds the old one back.
Fix it fast
1Find out which cause you have
Read which url_launcher_ios version is locked in your project.
grep -n -A3 "url_launcher_ios" pubspec.lock2Match what you see, then jump to its fix
What does the error look like?
UIApplication does not conform to protocol 'Launcher'Error in url_launcher_ios while building the iOS app in Xcode
Cause 1 of 2
The locked url_launcher_ios is older than 6.3.1
1Check
The package changelog lists 6.3.1 as the release that fixes a compile error when conforming UIApplication to Launcher in the iOS 18 SDK.
grep -n -A3 "url_launcher_ios" pubspec.lock2Fix
Upgrade the plugin to the highest version your pubspec.yaml allows, then rebuild.
flutter pub upgrade
flutter build ios --no-codesign3Verify
pubspec.lock now shows 6.3.1 or later and the build passes.
grep -n -A3 "url_launcher_ios" pubspec.lockConfirmed by pub.dev
Cause 2 of 2
The url_launcher constraint holds the iOS package back
1Check
The lockfile moves only within the constraints in pubspec.yaml, so an old upper bound on url_launcher keeps the old iOS implementation.
grep -n "url_launcher" pubspec.yaml
dart pub upgrade --major-versions --dry-run2Fix
Raise the url_launcher constraint, then upgrade. Commit pubspec.yaml first so you can undo it; --major-versions also updates the constraints.
dart pub upgrade --major-versions url_launcher3Verify
Run the iOS build again.
flutter build ios --no-codesignConfirmed by dart.dev
How do I stop it coming back?
- Upgrade packages with flutter pub upgrade before moving to a new Xcode major version, not after the build breaks.
- Commit pubspec.lock for apps so every machine and CI builds the same plugin versions.
- Build for iOS in CI on the Xcode version you ship with.
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
Flutter url_launcher does nothing or canLaunchUrl returns false
Exception: Could not launch https://example.com
On Android 11 and newer, and on iOS, canLaunchUrl returns false for any scheme you have not declared.
3 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 fixMobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fix