[flutter_tools] Migrate platforms away from .flutter-plugins

#48614 moves the plugins list to .flutter-plugins-dependencies. .flutter-plugins will be kept for a whilee to avoid breaking existing apps, but should be removed after the migration is complete

Is this a duplicate of #39657?

Oh never mind this is the cleanup step.

Is the migration on this complete?

It's still being parsed:

flutter/packages/flutter_tools/gradle/flutter.gradle

Line 375 in d9bf879

    
           File pluginsFile = new File(project.projectDir.parentFile.parentFile, '.flutter-plugins')

flutter/packages/flutter_tools/templates/cocoapods/Podfile-macos

Line 71 in d9bf879

plugin_pods = parse_KV_file('../.flutter-plugins')

flutter/packages/flutter_tools/lib/src/android/gradle.dart

Line 765 in d9bf879

final File flutterPluginFile = flutterProject.flutterPluginsFile;

flutter/packages/flutter_tools/lib/src/commands/packages.dart

Line 84 in 5ba2d79

    
           final int numberOfPlugins = (rootProject.flutterPluginsFile.readAsLinesSync()).length;

Looks like we're still parsing this in 2023: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy#L543

There may are projects, which were created with an old settings.gradle file, which references the .flutter-plugins file directly. This also may needs a test to not break the user experience somehow or write a proper migration / error message to upgrade it.
For reference:
#137115 (comment)
#98048 (comment)

Edit: it also states to remove dependencyGraph after migration, which is still used in flutter.groovy and I wonder how multiple transitive dependencies are handled then...or they just directly are stated in the plugins section then and the handling can just be safely removed (?)

Reland: "Fix how Gradle resolves Android plugin" (#137115)

Looks like we're still parsing this in 2023

This is now solved in #137115

I think #54566 is obsolete due to #135392 and we can remove all the .flutter-plugins related stuff (generation and tests) after the deprecation period.

Reland: "Fix how Gradle resolves Android plugin" (flutter#137115)

Announce deprecation of `.flutter-plugins`. (#11303)

Reverts "Added a warning if `flutter.groovy` uses a `.flutter-plugins…

Reverts "Reverts "Added a warning if `flutter.groovy` uses a `.flutte…

Allow opting out of `.flutter-plugins`, opt-out in `refreshPluginsLis…

Remove the only reference to `settings.gradle.legacy_versions`. (flut…

Added a warning if `flutter.groovy` uses a `.flutter-plugins` file. (f…

As of the latest master, this is true behind the flag flutter config explicit-package-dependencies.

As of the latest master (#160289), this is true by default.

After the next stable release, the ability to opt-out will be removed, and the feature can be removed.

Remove `FlutterProject.flutterPluginsFile`. (#169897)

Finish removing `--explicit-package-dependencies`. (#169950)

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 -v and a minimal reproduction of the issue.

Finish removing `--explicit-package-dependencies`. (#169950)

Navigation Menu

Repository navigation

[flutter_tools] Migrate platforms away from .flutter-plugins #48918

9 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[flutter_tools] Migrate platforms away from .flutter-plugins #48918

Description

Activity

jmagman commented on Jan 18, 2020

jmagman commented on Jan 18, 2020

dnfield commented on Dec 8, 2020

jmagman commented on Dec 8, 2020

christopherfujino commented on Aug 1, 2023

Gustl22 commented on Oct 25, 2023

Gustl22 commented on Dec 21, 2023

9 remaining items

matanlurey commented on Nov 15, 2024

matanlurey commented on Feb 22, 2025

github-actions commented on Jun 18, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions