flutter/dev/integration_tests/ios_host_app
Kishan Dhankecha 2867ac7885
Added missing code block language in docs (#147481)
- added language for all code blocks
- replaced `bash` or `shell` with `sh` for consistency.
- added `sh` and `console` in the GitHub template link generator.
- updated test for GitHub template.
2024-05-01 14:44:27 +00:00
..
flutterapp/lib Eliminate more window singleton usages (#145560) 2024-03-21 20:59:25 +00:00
FlutterUITests Retry button tap in [FlutterUITests testFlutterViewWarm] (#143967) 2024-02-23 16:13:21 +00:00
Host Remove "note that" in our documentation (as per style guide) (#120842) 2023-02-17 22:27:33 +00:00
Host.xcodeproj Migrate Xcode projects last version checks to Xcode 15.1 (#140256) 2024-01-03 23:05:46 +00:00
Host.xcworkspace Fixes to support add2app on iOS (#22277) 2018-09-26 01:57:05 -04:00
Podfile Set template and migrate apps to iOS 12 minimum (#140823) 2024-01-03 00:47:40 +00:00
README.md Added missing code block language in docs (#147481) 2024-05-01 14:44:27 +00:00

iOS host app

Used by the module_test_ios.dart device lab test.

iOS host app for a Flutter module created using

$ flutter create -t module hello

and placed in a sibling folder to (a clone of) the host app. flutterapp/lib/marquee.dart and flutterapp/lib/main.dart must be copied into the new module lib for platform unit tests to pass.

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

  1. A regular iOS view controller (UIViewController), similar to the default flutter create template (NativeViewController.m).
  2. 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).
  3. A demo of pushing a FlutterViewController on as a child view.
  4. A demo of showing both the native and the Flutter views using a platform channel to interact with each other (HybridViewController.m).
  5. A demo of showing two FlutterViewControllers simultaneously (DualViewController.m).

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

  1. The ability to pre-warm the engine and attach/detach a ViewController from it.
  2. The ability to use platform channels to communicate between views.
  3. The ability to simultaneously run two instances of the engine.