No accessToken even after successful account linking
See original GitHub issueI am using version 2.1.2 and Authorization code flow for account linking as specified in https://developers.google.com/actions/identity/oauth2-code-flow.
The entire flow works where my service does issue a valid accessToken and refreshToken to the google and I also get a confirmation in the assistant stating, “Great Nishant, your <bot name> account has been successfully linked with google”. All fine so far.
Now the expectation is that after this point onward whenever I do invoke the bot again, I should get the same accessToken back in conv.user.access.token
property, however this field remains empty. I have no idea what am I missing. I have setup dialogFlow integration with “Sign In required” during the invocation time.
Please help.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
No access token delivered to webhook after normal account ...
From end of last week, access token is not delivered to our webhook server even if account linking was successful and it is...
Read more >Troubleshooting Common Account Linking Issues with Alexa ...
This blog will go through issues such as how to troubleshoot “We were unable to link at this time” error, issues with account...
Read more >Unable to link accounts - Auth0 Community
The idea here would be to not access the management API in the frontend, but just get the id token for linking, send...
Read more >Refresh token is not working after initial account linking success
We have successfully enabled account linking for our custom skill and I can see access_token is passed into my custom skill. After 30 ......
Read more >Account linking with OAuth-based Google Sign-in ...
You do not want to allow users that have non-Google accounts to create ... After successful sign in, you return a long-lived access...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the settings for your Google Home, in the Google Assistant mobile app, there is going to be an option to identify yourself by voice. By default the user is considered anonymous.
I am having the same problem with the request from Google Home.
While the request from Web Simulator has accessToken as expected.
I am using Actions SDK.
Any suggestion would be highly appreciated.
Thanks.