reactor-uploader failing with unknown error | Community
Skip to main content
New Participant
May 23, 2022
Solved

reactor-uploader failing with unknown error

  • May 23, 2022
  • 1 reply
  • 1006 views

I am in the process of updating the key pair on my Launch extension and am unable to upload the extension.  I'm using the same command I've used in the past, but am now seeing this output:

No development extension package was found on the server with the name gainsight-px. A new extension package will be created. --verbose output: (node:71114) UnhandledPromiseRejectionWarning: Error: Error uploading extension package. An unknown error occurred. at module.exports (/Users/nickwolfe/.npm/_npx/71114/lib/node_modules/@adobe/reactor-uploader/bin/handleResponseError.js:26:9) at module.exports (/Users/nickwolfe/.npm/_npx/71114/lib/node_modules/@adobe/reactor-uploader/bin/uploadZip.js:65:5) at processTicksAndRejections (internal/process/task_queues.js:93:5) at async /Users/nickwolfe/.npm/_npx/71114/lib/node_modules/@adobe/reactor-uploader/bin/index.js:82:32 (Use `node --trace-warnings ...` to show where the warning was created) (node:71114) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:71114) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

 

I've deleted the new key pair from the developer console and reverted my private key file, so I should be back to where I was before I started this process, but I'm still seeing this error.

 

Any ideas?

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

Yes, there's a known issue with reactor-uploader v5.0.6 https://github.com/adobe/reactor-uploader/issues/49

Downgrade to v5.0.4 and try again.

1 reply

yuhuisg
yuhuisgAccepted solution
New Participant
May 24, 2022

Yes, there's a known issue with reactor-uploader v5.0.6 https://github.com/adobe/reactor-uploader/issues/49

Downgrade to v5.0.4 and try again.

New Participant
May 24, 2022

Thanks, that seems to have fixed it (although I'm unable to repro the original issue now when not forcing the version on the npx call.)