GeezerVison

What

An app that declares product flavors in its gradle configuration has no way to tell the CLI which one to build. The task name is built as:

const baseTaskName = buildData.androidBundle ? "bundle" : "assemble";

so the CLI always asks for assembleDebug/assembleRelease — which gradle rejects once flavors exist, because there is no flavourless variant to assemble.

--gradleFlavor foo inserts the flavor into the task name:

ns build android --gradleFlavor foo --release   # assembleFooRelease
ns run android --gradleFlavor foo               # assembleFooDebug
ns build android --gradleFlavor foo --aab       # bundleFooRelease

The flavor is capitalized to match gradle's task naming, and a flavor that is already capitalized is left alone.

Build output

No special handling needed. A flavored build lands in build/outputs/apk/<flavor>/<buildType> with a name like app-foo-debug.apk. getAllAppPackages already falls back to a recursive walk of the output directory, and the android getValidBuildOutputData regex is

(<packageName>|app)-.*-(Debug|Release)(-unsigned)?\.apk

which matches the flavored name as is.

Tests

npm test — 1860 passing. Added cases in test/services/android/gradle-build-args-service.ts for the debug, release, app bundle and already-capitalized forms.

Notes

From https://github.com/Akylas/nativescript-cli. Independent of #6129, #6130, #6131 and #6132, though it adds an option next to gradlePath in lib/options.ts like some of those do — expect a small textual conflict depending on merge order.