Skip to content

Migrated plugins should rely on v2 of the GeneratedPluginRegistrant #42694

@mklim

Description

@mklim

Right now we're manually doing this in all of our V2 activities in the example apps:

  @Override
  public void configureFlutterEngine(FlutterEngine flutterEngine) {
    flutterEngine.getPlugins().add(new PluginName());
  }

That's something we don't want to really show as an actual example or tell people to do, because GeneratedPluginRegistrant should ideally automatically call getPlugins().add itself for users.

Currently on stable GeneratedPluginRegistrant always uses the old embedding. There's a PR that's about to land on master that will change it to use the new embedding when it's available, #42684.

Once #42684 lands and rolls to stable the migrated plugins should change their example apps to rely on the Registrant instead of manually adding anything in their activity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work lista: existing-appsIntegration with existing apps via the add-to-app flowc: contributor-productivityTeam-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.platform-androidAndroid applications specifically

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions