flutter_flutter/dev/integration_tests
Victoria Ashworth 01fde956f0
CP: Pause UIScene migration (#170490) (#170569)
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.
2025-06-16 18:32:43 +00:00
..
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00
2025-06-03 08:48:14 +00:00

Automated Flutter integration test suites

Each suite consists of either a complete Flutter app and a flutter_driver specification that drives tests from the UI, or a native app that is meant to integrate with Flutter for testing.

Intended for use with devicelab tests.

If you want to run a driver test locally, to debug a problem with a test, you can use this command from the appropriate subdirectory:

flutter drive -t <test> --driver <driver>

For example:

flutter drive -t lib/keyboard_resize.dart --driver test_driver/keyboard_resize_test.dart

New tests require new CI runner

Adding code to this directory will not automatically cause it to be run by any already existing ci tooling. This directory is intentinally a "choose your own adventure" piece of tooling.