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): optionally pass the device ABIs to plugin builds
`--filter-plugins-devices-arch` passes the same `-PabiFilters` the app build
gets to the gradle build of every plugin built from source.
Nothing in the gradle files the CLI generates for a plugin acts on the
property, and this deliberately does not add such a block: what a plugin's
native sources need per ABI is the plugin's business. It is there for a plugin
whose own `include.gradle` reads `abiFilters` - a plugin with a long native
build (an NDK/CMake one, say) can then build only the ABIs this run is about
to deploy to instead of all four.
Off by default. A narrowed aar is a partial artifact and the aar cache is
keyed by the plugin sources, which do not change when a device with another
ABI joins, so the ABIs are now part of the plugin build data the rebuild
decision reads.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
@@ -39,6 +39,7 @@ Attach the debug tools to a running app in the native emulator | `$ ns debug and
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
41
*`--no-filter-devices-arch` - If set, builds every ABI instead of only the ones the connected devices report. The narrowing only applies when the app's gradle configuration acts on the `abiFilters` property, and `ns build` never narrows.
42
+
*`--filter-plugins-devices-arch` - If set, the ABIs of the connected devices are also passed to the gradle build of every plugin built from source. Nothing in the gradle files the CLI generates for a plugin acts on them - this is for a plugin whose own `include.gradle` reads the `abiFilters` property to shorten a long native build.
42
43
*`--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
@@ -44,6 +44,7 @@ Start a default emulator if none are running, or run application on all connecte
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
46
*`--no-filter-devices-arch` - If set, builds every ABI instead of only the ones the connected devices report. The narrowing only applies when the app's gradle configuration acts on the `abiFilters` property, and `ns build` never narrows.
47
+
*`--filter-plugins-devices-arch` - If set, the ABIs of the connected devices are also passed to the gradle build of every plugin built from source. Nothing in the gradle files the CLI generates for a plugin acts on them - this is for a plugin whose own `include.gradle` reads the `abiFilters` property to shorten a long native build.
47
48
*`--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