You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(android): --gradleFlavor to build a product flavor
An app that declares product flavors in its gradle configuration could not
tell the CLI which one to build - it always ran `assembleDebug` /
`assembleRelease`, which fails outright once flavors exist.
`--gradleFlavor foo` inserts the flavor into the task name, so the CLI
runs `assembleFooDebug`, `assembleFooRelease`, `bundleFooDebug` or
`bundleFooRelease`. The flavor is capitalized to match the gradle task
naming.
The build output does not need any special handling: gradle writes a
flavored build to `build/outputs/apk/<flavor>/<buildType>`, which the
existing recursive package lookup and its `-.*-(Debug|Release)` regex
already cover.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
*`--env.hiddenSourceMap` - creates sources maps in the root folder (useful for Crashlytics usage with bundled app in release).
36
36
*`--aab` - Specifies that the build will produce an Android App Bundle(`.aab`) file.
37
+
*`--gradleFlavor` - Builds the given product flavor, when the app declares any. `--gradleFlavor foo` runs the `assembleFooDebug`/`assembleFooRelease` gradle task instead of `assembleDebug`/`assembleRelease`.
37
38
*`--force` - If set, skips the application compatibility checks and forces `npm i` to ensure all dependencies are installed. Otherwise, the command will check the application compatibility with the current CLI version and could fail requiring `ns migrate`.
38
39
*`--path <Directory>` - Specifies the directory that contains the project. If not set, the project is searched for in the current directory and all directories above it.
Copy file name to clipboardExpand all lines: docs/man_pages/project/testing/debug-android.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ Attach the debug tools to a running app in the native emulator | `$ ns debug and
38
38
*`--env.sourceMap` - creates inline source maps.
39
39
*`--env.hiddenSourceMap` - creates sources maps in the root folder (useful for Crashlytics usage with bundled app in release).
40
40
*`--aab` - Specifies that the command will produce and deploy an Android App Bundle.
41
+
*`--gradleFlavor` - Builds the given product flavor, when the app declares any. `--gradleFlavor foo` runs the `assembleFooDebug`/`assembleFooRelease` gradle task instead of `assembleDebug`/`assembleRelease`.
41
42
*`--force` - If set, skips the application compatibility checks and forces `npm i` to ensure all dependencies are installed. Otherwise, the command will check the application compatibility with the current CLI version and could fail requiring `ns migrate`.
Copy file name to clipboardExpand all lines: docs/man_pages/project/testing/run-android.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,7 @@ Start a default emulator if none are running, or run application on all connecte
43
43
*`--env.sourceMap` - creates inline source maps.
44
44
*`--env.hiddenSourceMap` - creates sources maps in the root folder (useful for Crashlytics usage with bundled app in release).
45
45
*`--aab` - Specifies that the command will produce and deploy an Android App Bundle.
46
+
*`--gradleFlavor` - Builds the given product flavor, when the app declares any. `--gradleFlavor foo` runs the `assembleFooDebug`/`assembleFooRelease` gradle task instead of `assembleDebug`/`assembleRelease`.
46
47
*`--force` - If set, skips the application compatibility checks and forces `npm i` to ensure all dependencies are installed. Otherwise, the command will check the application compatibility with the current CLI version and could fail requiring `ns migrate`.
0 commit comments