Skip to content

About

Minimal Flutter iOS repro for cached FlutterEngine accessibility tree loss

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

Repository files navigation

iOS Flutter Accessibility Repro

Minimal Flutter iOS project that reproduces a semantics loss issue when a cached FlutterEngine is attached to a new FlutterViewController.

Why This Project Exists

The iOS host starts one FlutterEngine in AppDelegate and keeps it alive for the whole app lifetime. The native host screen creates a new FlutterViewController each time the user taps Open Flutter screen.

This mirrors add-to-app integrations that intentionally reuse an engine instead of destroying it when a Flutter screen is dismissed.

How To Run

flutter run

Reproduction Steps

  1. Launch the app on an iOS simulator or device.
  2. Open Accessibility Inspector or enable VoiceOver.
  3. Tap Open Flutter screen.
  4. Confirm that Flutter elements such as Display name, Marketing emails, and Save profile are visible in the iOS accessibility tree.
  5. Tap the native back button.
  6. Tap Open Flutter screen again.
  7. Inspect the Flutter screen again.

Expected Result

Flutter elements remain available through iOS accessibility after the cached engine is attached to the second FlutterViewController.

Actual Result On Affected Engine Revisions

The Flutter UI still renders, but the Flutter elements disappear from the iOS accessibility tree after reopening the screen with the same engine.

Destroying the engine between opens avoids the issue, but that is not viable for apps that intentionally share or cache a Flutter engine.

About

Minimal Flutter iOS repro for cached FlutterEngine accessibility tree loss

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages