Repository navigation
[HCPP] Enable opting in to HCPP platform views with a feature flag #176805
Description
Activity
- moved this to Todo in Hybrid Composition++ (HCPP) Platform Views
on Oct 9, 2025 @jaredjhallen Please file new feature requests as new issues, rather than as comments in tangentially related issues, so that they can be triaged and tracked.
This will be done in a cli-flag. Unfortunately the feature flag system would not surface this information early enough for the engine to consume it, as the engine needs to know at the time the swapchain is created
- added a commit that references this issue
on Mar 12, 2026 - moved this from Todo to Done in Hybrid Composition++ (HCPP) Platform Views
on Mar 12, 2026 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Mar 26, 2026 - added a commit that references this issue
on Mar 26, 2026 - added a commit that references this issue
on Apr 14, 2026 - added a commit that references this issue
on Sep 28, 2026
It is currently possible to use the
EnableSurfaceControlflag to do this, though that flag is subject to change:flutter/dev/integration_tests/android_engine_test/android/app/src/main/AndroidManifest.xml
Line 37 in 238db35
Feature flags are easier for app developers to use. We should enable opting in via a feature flag.
See
https://github.com/flutter/flutter/blob/master/docs/contributing/Feature-flags.md#adding-a-flag
https://docs.flutter.dev/tools/pubspec#config
And an example PR
https://github.com/flutter/flutter/pull/172478/files#diff-0ded384225f19a4c34d43c7c11f7cb084ff3db947cfa82d8d52fc94c112bb2a7