NativeScript / NativeScript/nativescript-cli
CLI 8.2.x discards AAR files with the same name
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- JavaScript
- Estrellas
- 1.1k
- Forks
- 204
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 8
Descripción
Issue Description
I have a plugin workspace with multiple packages and a core package, all under the same scope. My core package has a platforms folder, with an AndroidManifest.xml and an include.gradle file.
Starting from CLI 8.2.x (with 8.1.x works fine) I've noticed that some permissions were missing after building the app, permissions declared in the AndroidManifest.xml of my plugin. It turns out that on build time, an aar is being generated for my core package called core.aar. So, the file name seems to collide with another package (probably the one from @nativescript/core) hence being discarded.
I see the need of discarding duplicated aar files, but perhaps the process should be a bit more "smart" and consider where those files are placed. That, or generated aar files for scoped plugins should contain the scope on its name. These are some suggestions, in case they help.
Reproduction
- Find or create a plugin workspace with a package named
core. - Add an AndroidManifest.xml file to the
platforms/androidfolder of the plugin. - Add some permission to the manifest (any other thing would work too, but a permission is the easiest thing to add).
- Pack the plugin and install inside an existing app.
- Build the app.
- Check if the permission is listed under the information page of the app.
Relevant log output (if applicable)
No response
Environment
OS: macOS 12.2.1
CPU: (8) arm64 Apple M1
Shell: /bin/zsh
node: 16.13.1
npm: 8.3.2
nativescript: 8.2.3
# android
java: 11.0.11
ndk: Not Found
apis: 23, 26, 28, 29, 30, 31, 32
build_tools: 28.0.3, 29.0.0, 30.0.3, 31.0.0, 32.0.0
system_images:
- android-31 | Google Play ARM 64 v8a
- android-32 | Google Play ARM 64 v8a
# ios
xcode: 13.3.1/13E500a
cocoapods: 1.11.2
python: 2.7.18
python3: 3.8.9
ruby: 2.6.8
platforms:
- DriverKit 21.4
- iOS 15.4
- macOS 12.3
- tvOS 15.4
- watchOS 8.5
Dependencies
"dependencies": {
"@awarns/core": "file:../../packages/core",
"@nativescript/core": "file:../../node_modules/@nativescript/core",
"@nativescript/unit-test-runner": "^3.0.3",
"@awarns/geofencing": "file:../../packages/geofencing"
},
"devDependencies": {
"@jsdevtools/coverage-istanbul-loader": "3.0.5",
"@nativescript/android": "~8.2.0",
"@nativescript/ios": "~8.2.0",
"karma": "6.3.17",
"karma-coverage": "2.0.3",
"karma-jasmine": "4.0.1",
"karma-junit-reporter": "2.0.1",
"karma-nativescript-launcher": "0.4.0",
"nyc": "15.1.0"
}
Please accept these terms
- I have searched the existing issues as well as StackOverflow and this has not been posted before
- This is a bug report
- I agree to follow this project's Code of Conduct
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce la compilación usando un plugin con platforms/android/AndroidManifest.xml e include.gradle y, después, rastrea cómo la CLI gestiona los archivos AAR generados. Compara el comportamiento de CLI 8.1.x y 8.2.x e identifica dónde se descartan los artefactos con el mismo nombre. La tarea estará terminada cuando los permisos del manifest del plugin permanezcan en la aplicación compilada sin romper la gestión de artefactos duplicados.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, javascript
- Área
- build-system, cli, mobile-dev
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 42/100