-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Don't import plugins that don't support android in settings.gradle #54407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't import plugins that don't support android in settings.gradle #54407
Conversation
|
If we're making an edit to the settings.gradle, I think the right fix would be to read from .flutter-plugin-dependencies instead. The contents are broken down by platform: Example: I thought we filled an issue for this, maybe @franciscojma86 knows where it is 😄 |
|
I thought I has a draft PR for that but can't find it :( But yeah, The only issue that I know of is #39657 but it's already referenced here. |
|
ahh good call |
packages/flutter_tools/templates/module/android/library/include_flutter.groovy.copy.tmpl
Show resolved
Hide resolved
|
I've moved most of the logic in |
jonahwilliams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overal LGTM
Do we plan to handle migrating users too? If not, we might want to keep a project using the old settings.gradle for testing
|
Yep - it will be migrated. I filed #54566 and added an integration test just in case, so we don't delete |
* fix segment hit test behavior (#57461) * Making DropdownButtonFormField to re-render if parent widget changes (#57037) * Update DropdownButtonFormField's state if widget updates Co-authored-by: Shi-Hao Hong <[email protected]> * throw more specific toolexit when git fails during upgrade (#57162) * [flutter_tools] Refresh VM state before executing hot reload (#53960) * Update engine hash for 1.17.2 * Remove MaterialControls from examples/flutter_view (#57621) Co-authored-by: Jenn Magder <[email protected]> * Prevent building non-android plugins in build aar (#58018) * Allow FLUTTER_APPLICATION_PATH to be null for misconfigured Xcode projects (#57701) * Don't import plugins that don't support android in settings.gradle (#54407) Co-authored-by: LongCatIsLooong <[email protected]> Co-authored-by: Pedro Massango <[email protected]> Co-authored-by: Shi-Hao Hong <[email protected]> Co-authored-by: Christopher Fujino <[email protected]> Co-authored-by: Jason Simmons <[email protected]> Co-authored-by: stuartmorgan <[email protected]> Co-authored-by: Jenn Magder <[email protected]> Co-authored-by: Emmanuel Garcia <[email protected]>
Description
Currently, the Flutter Gradle plugin skips plugins that don't have an
android/build.gradlefile. However, we shouldn't be importing these plugins in the first place. A new behavior in Android Studio or Gradle could break the current check.Android Studio currently creates an android/ noop directory in the
.pub-cachedirectory.Hopefully, when #40460 is fixed, we will have a tool to automate the migration of project files like
settings.gradle.Related Issues
#39657
Tests
Updated tests.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.