search

alexa / ask-toolkit-for-vscode

ASK Toolkit is an extension for Visual Studio Code (VSC) that that makes it easier for developers to develop and deploy Alexa Skills.
https://developer.amazon.com/en-US/docs/alexa/ask-toolkit/get-started-with-the-ask-toolkit-for-visual-studio-code.html
Apache License 2.0
109 stars 53 forks source link

Login generates 404 error in browser #198

Closed kknundy closed 2 years ago

kknundy commented 2 years ago

Describe the bug

I am trying to log in to Alexa Skills toolkit on VS code. After I enter my login credentials for amazon into the browser, it fails to redirect to VS code, and presents a 404 error.

To Reproduce

Steps to reproduce the behavior:

  1. Open Visual Studio Code
  2. Install Extension 'Alexa Skills Toolkit'
  3. On left sidebar, click 'Sign In'
  4. Browser window opens with amazon login page. Enter credentials and click 'Allow'
  5. 404 Error. Browser fails to sign in or redirect to VS Code.

Expected behavior

The browser should show a 'Succesfully signed in' dialogue and Visual Studio Code should be able to view and create alexa skills associated with my Amazon account

Screenshots

Screenshot 2022-07-29 145607 Screenshot 2022-07-29 145722 Screenshot 2022-07-29 145810

Desktop (please complete the following information):

tydonelson commented 2 years ago

Hey Koushik, thanks for the report. I see you're running on Windows, are you using WSL by chance? We've had a few issues around WSL and the remote Amazon login that we're aware of. If so, could you try reverting to version 2.11.2 of the extension? That version uses localhost instead of 127.0.0.1 for the redirect.

It could also be an issue with SSH, if you're using SSH to do any kind of remote development, if that's the case then we have some instructions here for forwarding the 9090 port - https://github.com/alexa/ask-toolkit-for-vscode#faqs

Let me know if either/neither of those apply, and we can keep trying to narrow down the issue :)

github-actions[bot] commented 2 years ago

This stale issue has been closed now. Please reopen the issue if you are still having problems with the toolkit.

kknundy commented 2 years ago

The same issue persists with v2.11.2, except the URL now points to localhost instead of 127.0.0.1. The system is Windows 10 pro, with WSL disabled.

tydonelson commented 2 years ago

Thanks @kknundy , are you using SSH or anything else that would interfere with the server/port resolution (per the instructions linked above)?

github-actions[bot] commented 2 years ago

This stale issue has been closed now. Please reopen the issue if you are still having problems with the toolkit.