fix failing lint : `findByPath` requires a specific ordering of project evaluation in `flutter.groovy` (#159296) fix failing lint : `'findByPath' requires a specific ordering of project evaluation`   ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: Reid Baker <reidbaker@google.com>
diff --git a/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy b/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy index f12a3b3..dfec35b 100644 --- a/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy +++ b/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy
@@ -1259,8 +1259,18 @@ boolean isBuildingAar = project.hasProperty("is-plugin") // In add to app scenarios, a Gradle project contains a `:flutter` and `:app` project. // `:flutter` is used as a subproject when these tasks exists and the build isn't building an AAR. - Task packageAssets = project.tasks.findByPath(":flutter:package${variant.name.capitalize()}Assets") - Task cleanPackageAssets = project.tasks.findByPath(":flutter:cleanPackage${variant.name.capitalize()}Assets") + Task packageAssets + Task cleanPackageAssets + try { + packageAssets = project.tasks.named("package${variant.name.capitalize()}Assets").get() + } catch (UnknownTaskException ignored) { + packageAssets = null + } + try { + cleanPackageAssets = project.tasks.named("cleanPackage${variant.name.capitalize()}Assets").get() + } catch (UnknownTaskException ignored) { + cleanPackageAssets = null + } boolean isUsedAsSubproject = packageAssets && cleanPackageAssets && !isBuildingAar String variantBuildMode = buildModeFor(variant.buildType)