You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.
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??
The text was updated successfully, but these errors were encountered:
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:
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.
That you executed cordova-hcp login and provided correct credentials. It should generate .chcplogin file with them.
😢 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.
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??
The text was updated successfully, but these errors were encountered: