Redistribute iOS CODEOWNERS

[vashworth]

Redistribute iOS CODEOWNERS to rebalance load between team.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[gemini-code-assist]

Code Review

This pull request redistributes ownership for several iOS packages in the CODEOWNERS file to rebalance the workload. My review focuses on improving the formatting and maintainability of this file. I've suggested aligning the owners and sorting them alphabetically for better readability.

[gemini-code-assist]

For better readability and maintainability, it's good practice to keep the CODEOWNERS file well-formatted.

I'd suggest two improvements for the Darwin section:

1. Align all owner handles to the same column.
2. Sort owner handles alphabetically (case-insensitively) on each line.

This makes the file easier to read and maintain.

packages/camera/camera_avfoundation/**                      @hellohuanlin @louisehsu
packages/file_selector/file_selector_ios/**                 @okorohelijah @vashworth
packages/file_selector/file_selector_macos/**               @okorohelijah @vashworth
packages/google_maps_flutter/google_maps_flutter_ios/**     @LongCatIsLooong @vashworth
packages/google_sign_in/google_sign_in_ios/**               @LongCatIsLooong @okorohelijah
packages/image_picker/image_picker_ios/**                   @okorohelijah @vashworth
packages/image_picker/image_picker_macos/**                 @okorohelijah @vashworth
packages/in_app_purchase/in_app_purchase_storekit/**        @LongCatIsLooong @louisehsu
packages/local_auth/local_auth_darwin/**                    @louisehsu @okorohelijah
packages/path_provider/path_provider_foundation/**          @LongCatIsLooong @vashworth
packages/pointer_interceptor/pointer_interceptor_ios/**     @hellohuanlin @louisehsu
packages/quick_actions/quick_actions_ios/**                 @LongCatIsLooong @louisehsu
packages/shared_preferences/shared_preferences_foundation/** @tarrinneal
packages/url_launcher/url_launcher_ios/**                   @LongCatIsLooong @vashworth
packages/url_launcher/url_launcher_macos/**                 @LongCatIsLooong @vashworth
packages/video_player/video_player_avfoundation/**          @hellohuanlin @louisehsu
packages/webview_flutter/webview_flutter_wkwebview/**       @hellohuanlin @LongCatIsLooong