Closed kknundy closed 1 year 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 :)
This stale issue has been closed now. Please reopen the issue if you are still having problems with the toolkit.
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.
Thanks @kknundy , are you using SSH or anything else that would interfere with the server/port resolution (per the instructions linked above)?
This stale issue has been closed now. Please reopen the issue if you are still having problems with the toolkit.
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:
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
Desktop (please complete the following information):