History

Migrate Xcode projects last version checks to Xcode 15.1 (#140256 )

Change the following in the `flutter create` templates.  I didn't make any auto-migrations for existing apps because none seem that critical:
1. Turn on `ASSETCATALOG_COMPILER_GENERATE_SWIFT_ASSET_SYMBOL_EXTENSIONS` in iOS and macOS.
1. Turn on `BuildIndependentTargetsInParallel` in macOS template.  https://github.com/flutter/flutter/pull/125827/files#r1181817619 
1. Turn on `DEAD_CODE_STRIPPING` in macOS template. 
1. Set `ENABLE_USER_SCRIPT_SANDBOXING=NO` in iOS and macOS template.  `flutter` scripts don't work with this on.  This might require a migration in the future to explicitly turn this one off. However at least for now if the setting isn't present it defaults to `NO`.

Add migration for `LastUpgradeVersion` so users won't see these validation issues in Xcode.

Run migrator on all the example apps.  A few aren't Flutter apps so I edited them in Xcode.

Fixes https://github.com/flutter/flutter/issues/140253
See also https://github.com/flutter/flutter/issues/125817 and https://github.com/flutter/flutter/pull/90304.

2024-01-03 23:05:46 +00:00

flutterapp

Upgrade leak_tracker. (#140758 )

2024-01-02 20:58:16 +00:00

ios_add2app

Remove "note that" in our documentation (as per style guide) (#120842 )

2023-02-17 22:27:33 +00:00

ios_add2app.xcodeproj

Migrate Xcode projects last version checks to Xcode 15.1 (#140256 )

2024-01-03 23:05:46 +00:00

ios_add2app.xcworkspace

…

ios_add2appTests

Migrate ios_add2app_life_cycle to earlgrey 2 and latest iOS SDK (#80822 )

2021-04-21 14:03:59 -07:00

.gitignore

…

build_and_test.sh

Migrate ios_add2app_life_cycle to earlgrey 2 and latest iOS SDK (#80822 )

2021-04-21 14:03:59 -07:00

Podfile

Fix ios_add2app Podfile (#131263 )

2023-07-27 18:37:41 +02:00

README.md

…

README.md

iOS Add2App Life Cycle Test

This application demonstrates some basic functionality for Add2App, along with a native iOS ViewController as a baseline and to demonstrate interaction.

The following functionality is currently implemented:

A regular iOS view controller (UIViewController), similar to the default flutter create template (NativeViewController.m).
A FlutterViewController subclass that takes over the full screen. Demos showing this both from a cold/fresh engine state and a warm engine state (FullScreenViewController.m).
A demo of pushing a FlutterViewController on as a child view.
A demo of showing both the native and the Flutter views using a platform channel to interact with each other (HybridViewController.m).
A demo of showing two FlutterViewControllers simultaneously (DualViewController.m).

A few key things are tested here (IntegrationTests.m):

The ability to pre-warm the engine and attach/detach a ViewController from it.
The ability to use platform channels to communicate between views.
The ability to simultaneously run two instances of the engine.
That a FlutterViewController can be freed when no longer in use (also tested from FlutterViewControllerTests.m).
That a FlutterEngine can be freed when no longer in use.