-
Notifications
You must be signed in to change notification settings - Fork 13
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
alexa auth command not working #24
Comments
+1 same problem |
@goldytech it must be related with the versions Workaround: that should make |
ok, my guess is that this fix Ironic :) |
Yup, locally tested. |
@marcy-terui, to fix this, make the command that's getting killed return a promise that doesn't resolve until the work is done. See serverless/serverless#5503 for how I fixed |
An imperfect but easy to implement fix could be adding a |
Any update to this? I'm still seeing the issue with the latest version of serverless. @dschep I tried your fix by trying to install the fix, but the branch has been deleted. |
+1 same problem |
Hi,
In AWS Security profile following are my settings
now when I run the command
sls alexa auth
. I don't see any listener process / webserver getting started which listens on 9000 port.Hence after the Amazon consent screen The redirect uri not working in browser.
I've been following this link https://medium.com/@rupakg/how-to-build-a-serverless-alexa-skill-51d8479e0432
to build my custom skill.
Please help
The text was updated successfully, but these errors were encountered: