ionic-team / ionic-team/ionic-cli

Could not find or parse valid build output file

Offen
#5,026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
triage
Vorherrschende Sprache
TypeScript
Sterne
2k
Forks
682
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

below is the verbose output. Downgrade to cli 6.4.0 not working. save err.

PS E:\eclipsejeespace\moodleapp-4.0.2> npm --verbose run dev:android
npm info it worked if it ends with ok
npm verb cli [
npm verb cli 'E:\\nvm\\nodejs\\node.exe',
npm verb cli 'E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli '--verbose',
npm verb cli 'run',
npm verb cli 'dev:android'
npm verb cli ]
npm info using npm@6.14.15
npm info using node@v14.18.0
npm verb run-script [ 'predev:android', 'dev:android', 'postdev:android' ]
npm info lifecycle moodlemobile@4.0.2~predev:android: moodlemobile@4.0.2
npm info lifecycle moodlemobile@4.0.2~dev:android: moodlemobile@4.0.2

> moodlemobile@4.0.2 dev:android E:\eclipsejeespace\moodleapp-4.0.2
> ionic cordova run android --livereload

> npm.cmd run ionic:serve:before
npm info it worked if it ends with ok
npm verb cli [
npm verb cli 'E:\\nvm\\nodejs\\node.exe',
npm verb cli 'E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli 'prefix',
npm verb cli '-g'
npm verb cli ]
npm info using npm@6.14.15
npm info using node@v14.18.0
npm verb exit [ 0, true ]
npm timing npm Completed in 48ms
npm info ok
npm info it worked if it ends with ok
npm verb cli [
npm verb cli 'E:\\nvm\\nodejs\\node.exe',
npm verb cli 'E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli 'run',
npm verb cli 'ionic:serve:before'
npm verb cli ]
npm info using npm@6.14.15
npm info using node@v14.18.0
npm verb run-script [
npm verb run-script 'preionic:serve:before',
npm verb run-script 'ionic:serve:before',
npm verb run-script 'postionic:serve:before'
npm verb run-script ]
npm info lifecycle moodlemobile@4.0.2~preionic:serve:before: moodlemobile@4.0.2
npm info lifecycle moodlemobile@4.0.2~ionic:serve:before: moodlemobile@4.0.2

> moodlemobile@4.0.2 ionic:serve:before E:\eclipsejeespace\moodleapp-4.0.2
> gulp

[19:54:46] Using gulpfile E:\eclipsejeespace\moodleapp-4.0.2\gulpfile.js
[19:54:46] Starting 'default'...
[19:54:46] Starting 'lang'...
[19:54:46] Starting 'env'...
[19:54:47] Finished 'env' after 89 ms
[19:54:47] Finished 'lang' after 360 ms
[19:54:47] Finished 'default' after 361 ms
npm verb lifecycle moodlemobile@4.0.2~ionic:serve:before: unsafe-perm in lifecycle true
npm verb lifecycle moodlemobile@4.0.2~ionic:serve:before: PATH: E:\nvm\v14.18.0\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\eclipsejeespace\moodleapp-4.0.2\node_modules\.bin;E:\eclipsejeespace\moodleapp-4.0.2\node_modules\.bin;E:\nvm\v14.18.0\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\eclipsejeespace\moodleapp-4.0.2\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\TortoiseSVN\bin;E:\nvm;E:\nvm\nodejs;C:\Program Files\Git\cmd;E:\gradle-8.0-milestone-1\bin;E:\apache-maven-3.6.2\bin;C:\Program Files\Java\jdk1.8.0_271\bin;C:\Program Files\Java\jdk1.8.0_271\jre\bin;E:\nvm\nodejs;E:\androidStudioSDK\platform-tools;C:\Users\025nj\AppData\Local\Microsoft\WindowsApps
npm verb lifecycle moodlemobile@4.0.2~ionic:serve:before: CWD: E:\eclipsejeespace\moodleapp-4.0.2
npm info lifecycle moodlemobile@4.0.2~postionic:serve:before: moodlemobile@4.0.2
npm verb exit [ 0, true ]
npm timing npm Completed in 1557ms
npm info ok
> npm.cmd run ionic:serve -- --host=localhost --port=8100 --platform=android --project=app
[npm] npm info it worked if it ends with ok
[npm] npm verb cli [
[npm] npm verb cli 'E:\\nvm\\nodejs\\node.exe',
[npm] npm verb cli 'E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
[npm] npm verb cli 'prefix',
[npm] npm verb cli '-g'
[npm] npm verb cli ]
[npm] npm info using npm@6.14.15
[npm] npm info using node@v14.18.0
[npm] npm verb exit [ 0, true ]
[npm] npm timing npm Completed in 44ms
[npm] npm info ok
[npm] npm info it worked if it ends with ok
[npm] npm verb cli [
[npm] npm verb cli 'E:\\nvm\\nodejs\\node.exe',
[npm] npm verb cli 'E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
[npm] npm verb cli 'run',
[npm] npm verb cli 'ionic:serve',
[npm] npm verb cli '--',
[npm] npm verb cli '--host=localhost',
[npm] npm verb cli '--port=8100',
[npm] npm verb cli '--platform=android',
[npm] npm verb cli '--project=app'
[npm] npm verb cli ]
[npm] npm info using npm@6.14.15
[npm] npm info using node@v14.18.0
[npm] npm verb run-script [ 'preionic:serve', 'ionic:serve', 'postionic:serve' ]
[npm] npm info lifecycle moodlemobile@4.0.2~preionic:serve: moodlemobile@4.0.2
[npm] npm info lifecycle moodlemobile@4.0.2~ionic:serve: moodlemobile@4.0.2
[npm] > moodlemobile@4.0.2 ionic:serve E:\eclipsejeespace\moodleapp-4.0.2
[npm] > cross-env-shell ./scripts/serve.sh "--host=localhost" "--port=8100" "--platform=android" "--project=app"
[INFO] Waiting for connectivity with npm...

[INFO] Development server running!

Local: http://localhost:8100

Use Ctrl+C to quit this process

> cordova.cmd build android
[cordova] The "path" argument must be of type string. Received undefined
[ERROR] Could not find or parse valid build output file.

Tried the following paths:
- E:\eclipsejeespace\moodleapp-4.0.2\platforms\android\app\build\outputs\apk\debug\output.json
- E:\eclipsejeespace\moodleapp-4.0.2\platforms\android\app\build\outputs\apk\debug\output-metadata.json
npm verb lifecycle moodlemobile@4.0.2~dev:android: unsafe-perm in lifecycle true
npm verb lifecycle moodlemobile@4.0.2~dev:android: PATH: E:\nvm\v14.18.0\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\eclipsejeespace\moodleapp-4.0.2\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\TortoiseSVN\bin;E:\nvm;E:\nvm\nodejs;C:\Program Files\Git\cmd;E:\gradle-8.0-milestone-1\bin;E:\apache-maven-3.6.2\bin;C:\Program Files\Java\jdk1.8.0_271\bin;C:\Program Files\Java\jdk1.8.0_271\jre\bin;E:\nvm\nodejs;E:\androidStudioSDK\platform-tools;C:\Users\025nj\AppData\Local\Microsoft\WindowsApps
npm verb lifecycle moodlemobile@4.0.2~dev:android: CWD: E:\eclipsejeespace\moodleapp-4.0.2
npm info lifecycle moodlemobile@4.0.2~dev:android: Failed to exec dev:android script
npm verb stack Error: moodlemobile@4.0.2 dev:android: `ionic cordova run android --livereload`
npm verb stack Exit status 1
npm verb stack at EventEmitter. (E:\nvm\v14.18.0\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
npm verb stack at EventEmitter.emit (events.js:400:28)
npm verb stack at ChildProcess. (E:\nvm\v14.18.0\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
npm verb stack at ChildProcess.emit (events.js:400:28)
npm verb stack at maybeClose (internal/child_process.js:1058:16)
npm verb stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
npm verb pkgid moodlemobile@4.0.2
npm verb cwd E:\eclipsejeespace\moodleapp-4.0.2
npm verb Windows_NT 10.0.22621
npm verb argv "E:\\nvm\\nodejs\\node.exe" "E:\\nvm\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "--verbose" "run" "dev:android"
npm verb node v14.18.0
npm verb npm v6.14.15
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! moodlemobile@4.0.2 dev:android: `ionic cordova run android --livereload`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the moodlemobile@4.0.2 dev:android script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 23305ms

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\025nj\AppData\Roaming\npm-cache\_logs\2023-06-28T11_55_00_061Z-debug.log
PS E:\eclipsejeespace\moodleapp-4.0.2>

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

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