Skip to content

Some reformatting and add info on temporarily disabling UIScene#13095

Open
sfshaza2 wants to merge 7 commits intomainfrom
scene2
Open

Some reformatting and add info on temporarily disabling UIScene#13095
sfshaza2 wants to merge 7 commits intomainfrom
scene2

Conversation

@sfshaza2
Copy link
Contributor

Fix #13088

@sfshaza2 sfshaza2 requested a review from vashworth February 18, 2026 23:41
@sfshaza2 sfshaza2 requested a review from a team as a code owner February 18, 2026 23:41
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @sfshaza2, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the documentation related to UIScene migration for Flutter iOS applications. The changes aim to make the migration process clearer and more accessible by improving the document's structure, rephrasing complex explanations, and providing a new guide for temporarily disabling UIScene. The updates address a specific GitHub issue, ensuring the documentation is comprehensive and easy to follow for developers navigating these breaking changes.

Highlights

  • Documentation Clarity and Formatting: The document has undergone significant reformatting and rephrasing to improve readability and clarity across various sections, including the introduction, migration guides, and API references.
  • Temporarily Disabling UIScene: A new section has been added providing instructions on how to temporarily disable UIScene by modifying the Info.plist file, complete with an illustrative image.
  • Enhanced Reference Linking: Many inline links to Apple's documentation and other internal migration guides have been converted to more readable reference-style links, improving the document's structure and maintainability.
  • Clarified Migration Steps: Specific migration steps for AppDelegate, custom logic, Info.plist, and plugin lifecycle events have been rephrased and clarified for better understanding.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/content/release/breaking-changes/uiscenedelegate.md
    • Updated the important notice regarding UIScene support and auto-migration for iOS apps.
    • Replaced inline links with reference-style links for app launch sequence and life cycle documentation.
    • Added reference-style links for Apple's WWDC announcement and various migration guides.
    • Improved the phrasing for the success message after auto-migration.
    • Clarified the instructions for migrating AppDelegate and plugin registration.
    • Reformated bullet points for creating method channels and platform views.
    • Enhanced the explanation for migrating custom logic within application lifecycle events, including new reference links.
    • Clarified the Info.plist migration instructions.
    • Added a new section detailing how to temporarily disable UIScene, including an image.
    • Rephrased the introduction to creating a SceneDelegate.
    • Standardized references to Info.plist throughout the document.
    • Improved phrasing for SwiftUI app migration and added reference links.
    • Clarified the conditions for using the FlutterSceneLifeCycleProvider protocol.
    • Rephrased the section concerning multiple scenes and FlutterEngine association.
    • Updated the phrasing for the Flutter plugins migration guide.
    • Clarified instructions for registering plugins and handling AppDelegate events.
    • Rephrased the section on adding scene events for plugins.
    • Improved the phrasing for moving launch logic from application:willFinishLaunchingWithOptions:.
    • Clarified how to access windowScene through the viewController.
    • Reformated the 'Hide Migration Warning' section for better presentation.
Activity
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily focuses on reformatting the uiscenedelegate.md document for better readability and maintainability, such as breaking up long lines and using reference-style links. It also introduces a helpful new section on how to temporarily disable UIScene. The changes are positive, but I've identified a few minor typos and grammatical errors that should be addressed to further improve the document's quality.

@flutter-website-bot
Copy link
Collaborator

flutter-website-bot commented Feb 18, 2026

Visit the preview URL for this PR (updated for commit 76636b0):

https://flutter-docs-prod--pr13095-scene2-pmqcvjma.web.app

sfshaza2 and others added 6 commits February 18, 2026 16:32
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Member

@parlough parlough left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this update and the cleanup @sfshaza2! I pushed a fix to the failing image link and am approving the rest by deferring to @vashworth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add instructions to temporarily disable UIScene migration

3 participants

Comments