Android builds failing due to NPM cache problem

Hi, we currently have Android build failing with the attached message. Could you check whether this is Voltbuilder internal? Thanks

2023-05-26 09:06:35,382 - Output: Using cordova-fetch for cordova-android@^11.0.0
Failed to fetch platform cordova-android@^11.0.0
Probably this is either a connection problem, or platform spec is incorrect.
Check your connection and platform name/version/URL.
CordovaError: Error: npm: Command failed with exit code 1 Error output:
npm ERR! code ECONNREFUSED
npm ERR! syscall connect
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to http://npm-cache-verdaccio.default:4873/cordova-android failed, reason: connect ECONNREFUSED 10.128.49.113:4873
npm ERR! at ClientRequest. (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR! at ClientRequest.emit (node:events:513:28)
npm ERR! at Socket.socketErrorListener (node:_http_client:502:9)
npm ERR! at Socket.emit (node:events:525:35)
npm ERR! at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR! at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
npm ERR! FetchError: request to http://npm-cache-verdaccio.default:4873/cordova-android failed, reason: connect ECONNREFUSED 10.128.49.113:4873
npm ERR! at ClientRequest. (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR! at ClientRequest.emit (node:events:513:28)
npm ERR! at Socket.socketErrorListener (node:_http_client:502:9)
npm ERR! at Socket.emit (node:events:525:35)
npm ERR! at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR! at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
npm ERR! code: ‘ECONNREFUSED’,
npm ERR! errno: ‘ECONNREFUSED’,
npm ERR! syscall: ‘connect’,
npm ERR! address: ‘10.128.49.113’,
npm ERR! port: 4873,
npm ERR! type: ‘system’,
npm ERR! requiredBy: ‘.’
npm ERR! }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! ‘proxy’ config is set properly. See: ‘npm help config’

1 Like

We’re aware of this issue and are working on it now.

The issue has been resolved - thanks for your patience.