Not every request has a session. Every request has a context

[calevans]

I have only been working with Alexa for two weeks now so I may be wrong. However, I noticed in my logging that I was getting a lot of invalid app id errors. When I dug into it I found that not all requests coming from Amazon have a session - e.g. AudioPlayer.PlaybackStarted - but all requests have context. Once I changed the RequestValidator to check that instead, all errors stopped.

Thanks for the great library.

Cheers!
=C=

[nomisoft]

Hi Cal,

Thanks, you're quite right. I hadn't used the AudioPlayer requests but just read in the documentation about them not having a 'session' object. Some of the other requests I've used don't have the 'context' though so what I've done instead is put a getApplicationId() function in the AlexaRequest class which will return the id from session or context wherever its found.

Could you confirm that's work for you?

[calevans]

Hi! Very close, yes. This is a great solution. However, you need one small change: if (property_exists($this, 'context')) { return $this->context->System->application->applicationId; } when Context is present, the applicationId is inside the System object. Cheers! :) =C=

…

On Mon, Jan 30, 2017 at 9:16 AM, Simon ***@***.***> wrote: Hi Cal, Thanks, you're quite right. I hadn't used the AudioPlayer requests but just read in the documentation about them not having a 'session' object. Some of the other requests I've used don't have the 'context' though so what I've done instead is put a getApplicationId() function in the AlexaRequest class which will return the id from session or context wherever its found. Could you confirm that's work for you? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaDulQ2Ka1w_Aev3u4kf7Tcf6udO6suks5rXfDYgaJpZM4LvzZM> .

-- *Culture of Respect <http://bit.ly/1tOIyjG>* How to find, hire, and retain developers