Has anyone successfully implemented voice-forward consent for country/postal code?
I can send the Connections.StartConnection directive and receive the SessionResumedRequest fine, but I consistently get a result status of 'REDIRECT_TO_APP'.
Has anyone successfully implemented voice-forward consent for country/postal code?
I can send the Connections.StartConnection directive and receive the SessionResumedRequest fine, but I consistently get a result status of 'REDIRECT_TO_APP'.
I just tried this and got it working. I just returned the following directive:
{ "type": "Connections.StartConnection", "uri": "connection://AMAZON.AskForPermissionsConsent/2", "input": { "@type": "AskForPermissionsConsentRequest", "@version": "2", "permissionScopes": [ { "permissionScope": "alexa:devices:all:address:country_and_postal_code:read", "consentLevel": "ACCOUNT" } ] }, "token": "example-token" }
I was then asked if I wanted to give consent (via voice) and when confirmed, received the following SessionResumedRequest:
"request": { "type": "SessionResumedRequest", "requestId": "amzn1.echo-api.request.a4ea8f3e-8be9-4e87-b457-c172e4a8ce36", "timestamp": "2023-03-10T11:51:44Z", "locale": "en-GB", "cause": { "type": "ConnectionCompleted", "token": "example-token", "status": { "code": "200", "message": "Ok" }, "result": { "permissionScopes": [ { "consentLevel": "ACCOUNT", "permissionScope": "alexa:devices:all:address:country_and_postal_code:read" } ], "status": "ACCEPTED" } } }
I didn't do anything special in my skill config, just enabled the "Country/Region & Postal Code Only" permissions in the dev console Permissions page.
To close this: my issue was that I was testing in the ASK console. The console always returns the status REDIRECT_TO_APP, whereas an Alexa device invokes a permissions dialogue with the user, followed by a proper ACCEPTED/DENIED status.
Hi @Stephen Potter Could you resolve this? I am facing the same issue. I use Alexa.NET (C#).
No I was unable to figure this out. The docs say:
"REDIRECT_TO_APP
: Possible reasons for this outcome are that the user couldn't be recognized, the required level of authentication couldn't be achieved, the user turned off the personalization toggle, or the permission scope isn't available for voice consent."
I'm not using personalization, so it's not clear why this is returned. Any luck on your side?
None, I had moved to some different work when I returned to this now I get Internal Error
"cause": { "type": "ConnectionCompleted", "token": "73468c53-e5bb-4f00-9093-c22aead0de18", "status": { "code": "500", "message": "Internal error." } } }
24 People are following this question.