Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

promise is not defined Error #46

Closed
cuter74 opened this issue Mar 18, 2016 · 2 comments
Closed

promise is not defined Error #46

cuter74 opened this issue Mar 18, 2016 · 2 comments

Comments

@cuter74
Copy link

cuter74 commented Mar 18, 2016

I had to run cordova-hcp deploy

unable to sync: BadRequest: null
at Request.extractError (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/services/s3.js:322:35)
at Request.callListeners (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/request.js:596:14)
at Request.transition (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/request.js:21:10)
at AcceptorStateMachine.runTo (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/request.js:37:9)
at Request. (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/request.js:598:12)
at Request.callListeners (/usr/lib/node_modules/cordova-hot-code-push-cli/node_modules/s3-sync-aws/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
unable to sync: BadRequest: null

why??

@nikDemyankov
Copy link
Member

I might be wrong, but it seems that this error states BadRequest, not that promise is not defined.

Seems like it can't connect to the aws server. And reason for that can be: wrong url, bad credentials. Please, check:

  1. That you executed cordova-hcp init and it generated correct cordova-hcp.json file. Mainly - content-url in it, since it should be the address of your aws server.
  2. That you executed cordova-hcp login and provided correct credentials. It should generate .chcplogin file with them.

@nordnet-deprecation-bot
Copy link
Contributor

👋 Hi! Thank you for your interest in this repo.

😢 We are not using nordnet/cordova-hot-code-push-cli anymore, and we lack the manpower and the experience needed to maintain it. We are aware of the inconveniece that this may cause you. Feel free to use it as is, or create your own fork.

🔒 This will now be closed & locked.

ℹ️ Please see #79 for more information.

@nordnet nordnet locked and limited conversation to collaborators Sep 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants