ask dialog not interacting with local setup(ask run)

ktssr commented 1 year ago

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ X] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request 
[ ] Other... Please describe:

I have a Amozon skill created in developer console and cloned it to local machine using "ask init" command with skill id. I am using "ask run" to start the debugging session and then issued "ask dialog" command in new terminal.

Expected Behavior

Ask dialog should interact with the local code

Current Behavior

Ask dialog is interacting with the code hosted on developer console.

CLI Snapshot If applicable, add screenshots to help explain your problem.

Steps to Reproduce (for bugs)

Possible Solution

Your Environment and Context

ask-cli version: 2.29.2
Operating System and version: Windows 10 65-bit
Node.js version used for development: 18.15.0
NPM version used for development: 9.5.0

tydonelson commented 1 year ago

Hey @ktssr , thanks for the bug report! I have had some success reproducing this with ask dialog in certain situations, we'll take a look.

One possible workaround here is using the ASK Extension for Visual Studio Code to debug your skill, if you haven't tried that already. There are some docs here around setup and config, also here is a great recent demo from Jeff Blankenburg during their regular Alexa Developer Office Hours.

silaswint commented 8 months ago

I have the same problem and it's blocking me.

I am using "Alexa-hosted skills" and use my public git repository as template. I also had problems with create a new skill with "ask new --template-url https://github.com/.../... --template-branch master" (as Interaction Model), but it worked with the web version of creating new skills.

A possible workaround is using "ngrok" and define a https-endpoint here: https://developer.amazon.com/alexa/console/ask/build/custom/(skill id)/development/(language)/endpoint

alexa / ask-cli