Skip to content

Plugins don't use --local-engine framework on macOS/iOS #132228

@stuartmorgan-g

Description

@stuartmorgan-g

STR:

  • Add new plugin API to the engine for iOS or macOS
  • Build the engine
  • Add use of the new API in a plugin, locally, for testing
  • Try to run the plugin's example with --local-engine

Compilation will fail, because podhelper.rb is unconditionally using the actual tool cache dir here and here. It looks like this regressed in #59044 and #72020; prior to those, we were using FLUTTER_FRAMEWORK_DIR, which the tool used to set to point to the local engine build.

This makes testing plugin API changes much harder than it used to be since it requires modifying flutter in some way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: buildBuilding flutter applications with the toola: pluginsSupport for writing, building, and running plugin packagesc: contributor-productivityTeam-specific productivity, code health, technical debt.c: regressionIt was better in the past than it is nowplatform-iosiOS applications specificallyplatform-macBuilding on or for macOS specificallyteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions