-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Closed
Labels
c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutterplatform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on Androidteam-androidOwned by Android platform teamOwned by Android platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
We have a custom job per build mode attached to the the preDebugBuild, preProfileBuild and preReleaseBuild for the corresponding build modes. Since our upgrade from 3.27 to 3.29 we suddenly see that a flutter run for a debug build triggers the custom job both for the debug and profile build. After some debugging I found that configureCMakeDebug has a dependency on preProfileBuild which it doesn't had before. I bisected the code and found that #159756 introduced this behaviour. (#160205 fixes it and #160260 reintroduces it again). If the forceNdkDownload call is commented out the issue disappears.
I don't know if this is a Flutter specific issue, could also be Android.
Reproduce:
flutter create my_app
cd my_app/android
./gradlew --dry-run configureCMakeDebugjippeholwerda
Metadata
Metadata
Assignees
Labels
c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutterplatform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on Androidteam-androidOwned by Android platform teamOwned by Android platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.