You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the Audio Player in our skill. The Audio Player token is an important part of our application state that we use to implement playlist functionality.
Whereas the token is passed through on subsequent requests correctly for AMAZON.NextIntent requests for example, it is not on AudioPlayer.PlaybackNearlyFinished and PlaybackController.NextCommandIssued (that I know of) when writing bespoken unit tests.
As a result our skill throws an error internally.
I appreciate that most skills don't use the AudioPlayer API so it would be good to know if this is something we can expect to see fixed.
Description:
We use the Audio Player in our skill. The Audio Player token is an important part of our application state that we use to implement playlist functionality.
Whereas the token is passed through on subsequent requests correctly for
AMAZON.NextIntentrequests for example, it is not onAudioPlayer.PlaybackNearlyFinishedandPlaybackController.NextCommandIssued(that I know of) when writing bespoken unit tests.As a result our skill throws an error internally.
I appreciate that most skills don't use the AudioPlayer API so it would be good to know if this is something we can expect to see fixed.
Environment:
Steps To Reproduce
This works:
This does not work:
Expected behavior
The audio player token is passed through on all request types on bespoken unit tests
Actual behavior
The token is only passed into subsequent requests on certain request types