Endpoint setting ignored when deploying

[mxmtsk]

I'm submitting a...

• [x] Bug report
• [ ] Feature request
• [ ] Documentation issue or request
• [ ] Other... Please describe:

Expected Behavior

The endpoint in the Alexa Developer Console should be set to the Lambda ARN

Current Behavior

My settings are ignored. After I deployed the endpoint in the Alexa Developer Console is always set to the jovo.cloud webhook, instead of the Lambda arn directly. This is my app.json production stage settings:

"prod": {
    "endpoint": "arn:xxxxxxx",
    "host": {
        "lambda": {
            "arn": "arn:xxxx",
            "askProfile": "xxxx"
        }
    }
}

I'm deploying with this command:

jovo deploy --platform alexaSkill --project-id my-skill-id --stage prod --ask-profile my-ask-profile

This is the output of the console:

   ✔ Deploying Alexa Skill (stage: prod)
     ✔ Updating Alexa Skill project for ASK profile xxxx
       Skill Name: xxxx (de-DE)
       Skill ID: xxxx
       Invocation Name: xxxx (de-DE)
       Endpoint: https://webhook.jovo.cloud/endpoint-id
     ✔ Deploying Interaction Model, waiting for build
       ✔ de-DE
     ✔ Uploading to lambda
       Deployed to lambda function: arn:xxxxx

Am i missing or missunderstanding something here?

Your Environment

• Jovo Framework version used: 1.4.2
• Operating System: MacOS, node 10.1.0, jovo-cli 1.2.0

[jankoenig]

Did you do jovo build --stage prod before the deploy command? The build command updates the files in the platforms folder, deploy then uploads these to the platforms.

[mxmtsk]

Thanks, that's what I missed or missunderstood. I was under the impression that deploying the skill will build it before