question

Chase-Work avatar image
Chase-Work asked

accessToken not getting generated after successful Account linking

Hi, I am creating a skill which has account linking option enabled. On enabling the skill, user is redirected to login page where after successful login and generating Oauth 2.0 accessToken and passing this token to the redirect uri as mentioned in the document, a message can be seen "Your xyz skill was successfully linked". But the problem is when I test this on service simulator I am unable to see the [b]accessToken[/b] field in the json object of user returned by Alexa. What are the possible reason for this?
alexa skills kitsubmission testing certification
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Answers

Chase-Work avatar image
Chase-Work answered
After reading some other threads, I came to know that the token is getting generated when I tested it on Alexa rather than on simulator. I was able to see the token. Anyway thanks guys
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Steve A avatar image
Steve A answered
Yes! For me, the simulator never shows or passes the access token. They said they've fixed this a while back -- and it was working briefly for me -- but not any more. I'm not sure if this is just a problem for people developing a skill as a web service (instead of Lambda), but I suspect the problem is connected to web service skills. It's sort of a pain, since I cannot use the simulator for development.
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.