mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
ab2b0851a2
This adds a smoke test for every single API example. It also fixes 17 tests that had bugs in them, or were otherwise broken, and even fixes one actual bug in the framework, and one limitation in the framework. The bug in the framework is that NetworkImage's _loadAsync method had await response.drain<List<int>>();, but if the response is null, it will throw a cryptic exception saying that Null can't be assigned to List<int>. The fix was just to use await response.drain<void>(); instead. The limitation is that RelativePositionedTransition takes an Animation<Rect> rect parameter, and if you want to use a RectTween with it, the value emitted there is Rect?, and one of the examples was just casting from Animation<Rect> to Animation<Rect?>, which is invalid, so I modified RelativePositionedTransition to take a Rect? and just use Rect.zero if the rect is null. |
||
|---|---|---|
| .. | ||
| flutterapp | ||
| ios_add2app | ||
| ios_add2app.xcodeproj | ||
| ios_add2app.xcworkspace | ||
| ios_add2appTests | ||
| .gitignore | ||
| build_and_test.sh | ||
| Podfile | ||
| 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 createtemplate (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.