jovotech / jovo-cli

🛠 Command Line Interface for the Jovo Framework: Makes voice experience deployment a breeze, including features like local development and staging.
https://www.jovo.tech/marketplace/jovo-cli
Apache License 2.0
57 stars 31 forks source link

Cannot upload to lambda in Windows command prompt #28

Closed serg06 closed 6 years ago

serg06 commented 6 years ago

This is what I get when I try to build/deploy using an arn endpoint:

E:\repo\<removed>>jovo build --stage dev --deploy

   √ Updating /platforms/alexaSkill
     √ Updating Alexa project files
       √ skill.json
     √ Updating Alexa Interaction Model based on Jovo Language Model in /models
       √ en-US
   > Deploying
     > Deploying Alexa Skill
       √ Updating Alexa Skill project for ASK profile default
         Skill Name: <removed> (en-US)
         Skill ID: amzn1.ask.skill.<removed>
         Invocation Name: <removed> (en-US)
         Endpoint: arn:aws:lambda:us-east-1:<removed>:function:<removed>
       √ Deploying Interaction Model, waiting for build
         √ en-US
       × Uploading to lambda
         -> File access error. Error: ENOENT: no such file or directory, access 'E:\repo\<removed>"'
{ Error: File access error. Error: ENOENT: no such file or directory, access 'E:\repo\<removed>"'
    at Object.getAskError (C:\Users\<removed>\AppData\Roaming\npm\node_modules\jovo-cli\helper\alexaUtil.js:761:16)
    at C:\Users\<removed>\AppData\Roaming\npm\node_modules\jovo-cli\helper\alexaUtil.js:735:44
    at ChildProcess.exithandler (child_process.js:282:5)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
  context:
   { locales: [ 'en-US' ],
     type: [ 'alexaSkill' ],
     projectId: undefined,
     endpoint: 'jovo-webhook',
     target: 'all',
     src: 'E:\\repo\\<removed>\\',
     stage: 'dev',
     askProfile: 'default',
     skillId: 'amzn1.ask.skill.<removed>',
     lambdaArn: 'arn:aws:lambda:us-east-1:<removed>:function:<removed>' } }

But the same thing works just fine in Ubuntu For Windows 10. (Or at least it says it does, green symbol and no errors.)

As you may notice, there is an extra double-quote at the end of the file path.

aswetlow commented 6 years ago

Thanks. Fixed in v1.1.3