migrate to UIScene #417
Merged
migrate to UIScene #417
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull request overview
This PR migrates the iOS app to Apple's UIScene-based application lifecycle, a requirement mandated by Apple. The migration was performed manually following Flutter 3.38 guidelines to match the structure of the Toolkit example app.
Key Changes
- Added UIScene configuration manifest to Info.plist with FlutterSceneDelegate
- Updated AppDelegate to implement FlutterImplicitEngineDelegate protocol
- Moved plugin registration from application launch to the new implicit engine initialization callback
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| ios/Runner/Info.plist | Added UIApplicationSceneManifest configuration and reorganized existing keys for scene-based lifecycle |
| ios/Runner/AppDelegate.swift | Implemented FlutterImplicitEngineDelegate protocol and moved plugin registration to new callback method |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
kmueller-gis
approved these changes
Dec 5, 2025
martinoyovo
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apple is mandating some changes to move iOS apps to their "scene" based application lifecycle. Flutter 3.38 provides a tool to automate migration. The tool didn't perform the migration, probably because our build files are a bit older. So instead I followed the instructions for a manual migration. The files ended up the same as the Toolkit example app, which was able to do the auto-migration.