01fde956f0
CP of https://github.com/flutter/flutter/pull/170490 This PR rolls back auto-migrating iOS apps to UIScene lifecycle. It also updates tests to ensure things work in both a state where UIScene lifecycle is already adopted and when it isn't. A number of UIScene issues have emerged since landing this in master: https://github.com/flutter/flutter/issues/170171 In addition, there's is disagreement over how some of it is implemented. Impacted Users: All Flutter iOS developers Impact Description: Some method channels may crash and apps using app lifecycle events may not work properly. Workaround: Manually removing UIApplicationSceneManifest from Info.plist and potentially also update AppDelegate.swift. Risk: Low Test Coverage: Yes Validation Steps: Run `flutter build ios` and see that `UIApplicationSceneManifest` if not added to Info.plist.
external_textures
Tests external texture rendering between a native1 platform and Flutter.
Part of Flutter's API for plugins includes passing external textures, or textures
created outside of Flutter, to Flutter, typically using the Texture
widget. This is useful for plugins that render video, or for plugins that
interact with the camera.
For example:
Because external textures are created outside of Flutter, there is often subtle translation that needs to happen between the native platform and Flutter, which is hard to observe. These integration tests are designed to help catch these subtle translation issues.
How it works
- Each
lib/*_main.dartfile is a Flutter app instrumenting a test case. - There is a corresponding
test_driver/*_test.dartthat runs assertions.
To run the test cases locally, use flutter drive2:
flutter drive lib/frame_rate_main.dart --driver test_driver/frame_rate_test.dart
Tip
On CI, the test cases are run within our device lab.
See
devicelab/lib/tasks/integration_tests.dartand search forcreateExternalUiFrameRateIntegrationTest.The actual tests are run by task runners: