Repository navigation
Example apps are broken if they use the old version of settings.gradle #98048
Description
After #97823, some builds break if the app uses the older version of settings.gradle.
For example, webview_flutter_android:
Where:
Script 'flutter/packages/flutter_tools/gradle/flutter.gradle' line: 509
* What went wrong:
A problem occurred configuring project ':path_provider'.
> Failed to notify project evaluation listener.
> Could not find method implementation() for arguments [project ':path_provider_android'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
> Could not find method implementation() for arguments [project ':path_provider_ios'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
> Could not find method implementation() for arguments [project ':path_provider_linux'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
> Could not find method implementation() for arguments [project ':path_provider_macos'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
> Could not find method implementation() for arguments [project ':path_provider_windows'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
This can be fixed by updating settings.gradle to the latest version:
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/app_shared/android.tmpl/settings.gradle
cc @GaryQian for the migration tool
cc @stuartmorgan
Activity
GaryQian commentedon Feb 8, 2022
Migration tool will be able to handle this case.
GaryQian commentedon Feb 8, 2022
Is this important enough to revert #97823 for now? It seems that it is more common for apps to use legacy settings.gradle than use iOS only plugins
blasten commentedon Feb 8, 2022
yes, let's revert it for now, and reland after the migration tool lands.
stuartmorgan-g commentedon Feb 8, 2022
It's more of an edge case than that; it's using a plugin that doesn't support Android but has an android/ folder. (Most likely due to sloppy updating of a plugin that used to have a dummy Android implementation since that used to be required.)
gnprice commentedon Apr 18, 2023
The revert #98050 was landed. Is there still an open task that this issue is tracking?
(I see that when the revert landed, the issue was lowered in priority but kept open: #98048 (comment) )
stuartmorgan-g commentedon Apr 18, 2023
It may have been intended to track getting to the point where we can reland that change, but since the original issue is still open I don't think we need it.
github-actions commentedon May 2, 2023
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.Reland: "Fix how Gradle resolves Android plugin" (#137115)
Reland: "Fix how Gradle resolves Android plugin" (flutter#137115)