Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"There is no interaction model for en-US. Select a different locale." #254

Closed
cancastilho opened this issue Apr 9, 2023 · 5 comments · Fixed by #261
Closed

"There is no interaction model for en-US. Select a different locale." #254

cancastilho opened this issue Apr 9, 2023 · 5 comments · Fixed by #261
Labels
bug Something isn't working

Comments

@cancastilho
Copy link

Describe the bug

After creating a skill using the web browser, I've found the possibility of using vs code to edit the skill. Then, I've installed the vscode extension and did the necessary configuration so that I could start using it to develop a sample skill. But, the option Test Skill -> Open simulator was throwing me the error "There is no interaction model for en-US. Select a different locale.". That's ok, because when I've created the skill I selected Brazilian Portuguese as the default language. So, as sugested by the error message, I tried to change the locale in the locale combobox (show below), but I couldn't, because it was stuck with a "Loading...":

image

To Reproduce

High level steps to reproduce the behavior (of what I remember I've done so far, I have not tested it):

  1. Create a custom skill using the web browser selecting as primary language Portuguese BR.
  2. Add 3 more languages using web browser: English (US), Spanish (ES) and Spanish (US), but without their interaction model.
  3. Install and configure VScode ASK extension.
  4. Sign in using the extension.
  5. Download the previously created skill using the option "Download and edit skill"
  6. Install ask-sdk-local-debug for nodejs as described in the README
  7. Configure the lauch.json as described in the docs.
  8. Use the option "Test Skill -> Open Simulator" to see the error.

Expected behavior

The expected behaviour would be allowing me to select the Portuguese Language after the error is shown, even though the English model doesn't exist yet.

image

Desktop (please complete the following information):

  • OS: Windows_NT x64 10.0.19044
  • Visual Studio Code Version: 1.77.1
  • Alexa Skills Toolkit Version: 2.14.1
  • Git Version: git version 2.35.1.windows.2

Additional context

As a workaround to solve the problem, I've added a en-US locale to the skill using the web browser, saved and deployed. I had to close the vscode an open it again. Then, in vscode, I downloaded the en-US locale json configuration using the option "Interaction model"-> Download. After that, the error stopped showing and I could select any of the 4 languages shown in the second image above.

@cancastilho cancastilho added the bug Something isn't working label Apr 9, 2023
@tydonelson
Copy link
Contributor

@cancastilho Thanks for the detailed report Carlos! I'll take a look into what's going on.

@tydonelson
Copy link
Contributor

To clarify, after you worked around the issue and were able to select Portuguese (BR), were you able to test your skill?

@cancastilho
Copy link
Author

cancastilho commented Apr 10, 2023

Yes, after the workaround I could use the simulator in vscode to test the skill.

To clarify, after you worked around the issue and were able to select Portuguese (BR), were you able to test your skill?

@doiron doiron mentioned this issue Apr 28, 2023
11 tasks
@doiron
Copy link
Contributor

doiron commented Apr 28, 2023

re-opening. we pushed the changes but we are holding back the actual release until Monday. I'll comment again here and close once the release is out.

@doiron doiron reopened this Apr 28, 2023
@doiron
Copy link
Contributor

doiron commented May 1, 2023

released 2.14.2 to VScode marketplace. Let us know if the problem persists after updating.

thank you for reporting the bug!

@doiron doiron closed this as completed May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants