missing android-dts-generator.jar - ns typings android not working

Offen
#1,802 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
android, java
Bereich
mobile-dev

Rechercherichtung

Beginne damit, den ns typings android --aar-Ablauf während der Vorbereitung des Android-Projekts nachzuverfolgen, und prüfe, wie platforms/android/build-tools/dts-generator.jar bereitgestellt werden soll. Bestätige, dass das jar verfügbar ist und dass der Befehl aus der bereitgestellten .aar-Datei Typings generieren kann, ohne den gemeldeten Zugriffsfehler.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug
Issue Description

I'm trying to make the types: ns typings android --aar ./colorpickerview-2.3.0.aar

When I try this I have the following output

vallemar@macbook-pro-de-juan nativescript-reordering % ns typings android --aar ./colorpickerview-2.3.0.aar
No platforms folder found, preparing project now...
Preparing project...
assets by path sources/ 17.7 MiB
   assets by path fonts/*.ttf 17.6 MiB
     asset fonts/MaterialSymbolsRounded.ttf 10.1 MiB [compared for emit] [from: src/fonts/MaterialSymbolsRounded.ttf] [copied]
     asset fonts/MaterialSymbolsOutlined.ttf 7.39 MiB [compared for emit] [from: src/fonts/MaterialSymbolsOutlined.ttf] [copied]
     asset fonts/UberMove-Light.ttf 53.7 KiB [compared for emit] [from: src/fonts/UberMove-Light.ttf] [copied]
   assets by path fonts/*.otf 111 KiB
     asset fonts/UberMoveBold.otf 56 KiB [compared for emit] [from: src/fonts/UberMoveBold.otf] [copied]
     asset fonts/UberMoveMedium.otf 55.2 KiB [compared for emit] [from: src/fonts/UberMoveMedium.otf] [copied]
assets by path *.js 10.2 MiB
   asset vendor.js 8.62 MiB [compared for emit] (name: vendor) (id hint: defaultVendor)
   asset bundle.js 1.61 MiB [compared for emit] (name: bundle)
   asset runtime.js 12.8 KiB [compared for emit] (name: runtime)
asset assets/lottie/confetti.json 29.7 KiB [compared for emit] [from: src/assets/lottie/confetti.json] [copied]
Entrypoint bundle 10.2 MiB = runtime.js 12.8 KiB vendor.js 8.62 MiB bundle.js 1.61 MiB
orphan modules 23.1 KiB [orphan] 15 modules
runtime modules 2.72 KiB 8 modules
modules by path ./node_modules/ 3.18 MiB
   javascript modules 2.91 MiB 430 modules
   json modules 273 KiB
     modules by path ./node_modules/mdn-data/css/*.json 242 KiB 3 modules
     modules by path ./node_modules/css-tree/ 30.7 KiB 2 modules
modules by path ./src/ 476 KiB
   modules by path ./src/components/*.vue 53.8 KiB 45 modules
   modules by path ./src/views/*.vue 38.1 KiB 10 modules
   modules by path ./src/*.ts 13.8 KiB 6 modules
   modules by path ./src/utils/*.ts 347 KiB 3 modules
   + 4 modules
external "~/package.json" 42 bytes [optional] [built] [code generated]
webpack 5.89.0 compiled successfully in 2344 ms
Webpack compilation complete.
Updating runtime package.json with configuration values...
Project successfully prepared (android)
Error: Unable to access jarfile /Users/vallemar/workspaces/test/nativescript-reordering/platforms/android/build-tools/dts-generator.jar

I have looked inside the folder and the dts-generator.jar file does not exist

Reproduction

No response

Relevant log output (if applicable)

No response

Environment
OS: macOS 14.1
CPU: (12) arm64 Apple M2 Max
Shell: /bin/zsh
node: 18.14.0
npm: 9.3.1
nativescript: 8.6.1

# android
java: 11.0.18
ndk: Not Found
apis: Not Found
build_tools: Not Found
system_images: Not Found

# ios
xcode: 15.0/15A240d
cocoapods: 1.13.0
python: 3.11.5
python3: 3.11.5
ruby: 2.7.7
platforms: 
  - DriverKit 23.0
  - iOS 17.0
  - macOS 14.0
  - tvOS 17.0
  - watchOS 10.0
Dependencies
"dependencies": {
  "@akylas/nativescript": "^8.5.10",
  "@nativescript-community/ui-collectionview": "^5.3.3",
  "@nativescript-community/ui-collectionview-swipemenu": "^5.3.3",
  "@nativescript-community/ui-lottie": "^5.0.6",
  "@nativescript-community/ui-material-bottomsheet": "^7.2.4",
  "@nativescript-community/ui-material-tabs": "^7.2.4",
  "@nativescript-community/ui-persistent-bottomsheet": "^0.0.29",
  "@nativescript-community/ui-popover": "^0.1.9",
  "@nativescript-use/vue": "^0.0.26",
  "@nativescript/stackblitz": "^0.0.8",
  "dayjs": "^1.11.10",
  "nativescript-vue": "3.0.0-beta.10",
  "patch-package": "^8.0.0",
  "pinia": "^2.1.7"
},
"devDependencies": {
  "@nativescript/android": "8.6.2",
  "@nativescript/core": "^8.6.1",
  "@nativescript/ios": "8.6.1",
  "@nativescript/preview-cli": "1.0.5",
  "@nativescript/tailwind": "^2.0.1",
  "@nativescript/types": "~8.5.0",
  "@nativescript/webpack": "~5.0.0",
  "@types/node": "~17.0.21",
  "tailwindcss": "^3.1.8",
  "typescript": "^5.2.2"
}
Please accept these terms
Vorherrschende Sprache
C++
Sterne
563
Forks
144
Ø Merge
10 Std. 46 Min.
Gemergte PRs (30 T.)
14

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NativeScript/android

Alle Issues in NativeScript/android

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.