feat: update iOS templates to use UIScene lifecycle

[realmeylisdev]

Summary

Updates iOS templates to use Apple's UIScene lifecycle, which will be mandatory for all UIKit apps built with iOS 26+ SDK.

This PR adds:

• iOS build CI workflow to verify UIScene configuration on template changes
• Documentation updates with iOS Requirements section
• CHANGELOG entry

Dependencies

⚠️ This is a draft PR - waiting for template updates to be merged and published.

• Merge feat: update iOS templates to use UIScene lifecycle very_good_templates#416
• Publish updated templates to BrickHub
• Regenerate bundles with ./tool/generate_bundles.sh
• Update this PR with regenerated bundles

Changes

File	Description
.github/workflows/ios_build.yaml	New CI workflow for iOS build verification
site/docs/templates/core.md	Added iOS Requirements section
CHANGELOG.md	Added feature entry

Requirements

• Flutter: 3.38.0+
• Xcode: 15.0+

References

• Closes feat: update iOS template to use UIScene lifecycle for Flutter 3.38+ #1436
• Depends on feat: update iOS templates to use UIScene lifecycle very_good_templates#416
• Flutter UIScene Migration Guide

Test plan

• Verify iOS build workflow runs successfully
• Verify documentation renders correctly
• After bundle regeneration:
  • very_good create flutter_app test_app generates UIScene-enabled project
  • flutter build ios --no-codesign succeeds
  • App launches in iOS Simulator

[marcossevilla]

we don't need this workflow to validate a specific migration on the iOS side, let's remove it and if you can share a video of the UIScene working fine when running iOS, I think that would be more valuable. Thanks!

[marcossevilla]

we don't need this workflow to validate a specific migration on the iOS side, let's remove it and if you can share a video of the UIScene working fine when running iOS, I think that would be more valuable. Thanks!

[marcossevilla]

changelog is auto generated by CI too

[marcossevilla]

the docs shouldn't have references to migrations, that will be generated in the changelog when we merge the PR

[marcossevilla]

@meylis1998 I think this PR should be closed since most changes will be generated and the ones that are not generated don't belong here

[realmeylisdev]

After reviewing the feedback and investigating the codebase structure, I agree this PR should be closed. Here's why:

Why This PR Should Be Closed:

1. The bundle files are auto-generated

   • All three changed bundle files (very_good_core_bundle.dart, very_good_flame_game_bundle.dart, very_good_flutter_plugin_bundle.dart) have // GENERATED CODE - DO NOT MODIFY BY HAND headers
   • They're generated by tool/generate_bundles.sh which runs mason bundle --source hosted

2. The actual templates live in a separate repository

   • As stated in CONTRIBUTING.md, all templates have their own repositories in VeryGoodOpenSource/very_good_templates
   • iOS UIScene lifecycle changes should be made in:
     • very_good_core
     • very_good_flame_game
     • very_good_flutter_plugin

3. Correct workflow:

   • Submit iOS UIScene lifecycle changes to the very_good_templates repository
   • After templates are updated and published to Mason registry, maintainers regenerate bundles in this repo

Next Steps:

Please open a PR in the very_good_templates repository with the iOS UIScene lifecycle changes and a video demo showing it working properly.

Thank you for your contribution! 🙏