Sample app does not handle exit/quit/close about skill-sample-nodejs-fact

[JennJin]

@TDA, sorry for the confusion. I've been asked to go through and close out 'old' open Issues.

I closed this one because it's not an issue with the sample code.

"Exit" and "Quit" are reserved words for a 'hard exit' on a Session. They route to a System Intent that immediately ends the current session. The skill will receive a "SessionEndRequest" with the 'Reason' = "USER_INITIATED".
"SessionEndRequest" Request Type

So you don't need to handle for "Exit" and "Quit".
Sending a response to a Request Type of 'SessionEndRequest' will result in Alexa replying back with an error that appears in your CloudWatch Logs.

It would be great to continue the discussion on the Alexa Developer Forum .

[RedRoxProjects]

Hey @TDA @PaulCutsinger @deegles - I encountered this issue when trying something with the alexa skill sample at a hackathon, couldn't find a way out once I'd got into the error - are there any updates on this?

[TDA]

@DickensA tbh, I never got a response to this, I just re-submitted a bunch of times and gave up. There is an article on the forums for this, apparently this need not be supported: https://forums.developer.amazon.com/forums/thread.jspa?threadID=8941&tstart=0
But the reviewers dont seem to know that. :\

[delianides]

Your app might need to respond to an Unhandled option as a possibility for Intents.

Unhandled() {
    this.emit(':ask',
      `I\'m sorry, but I\'m not sure what you asked me.`
  },

I found this out when I misspelled an intent and the app didn't know how to process the request. Kind of acts like a default option inside a switch statement.

[varungoyal44]

I found the error in my code, I was missing:-
the "Unhandled" function at first then i was missing
module.exports = handlers;

in the intentHandlers.js

[AndyMayJE]

Exit is a command baked into Alexa.

If you receive this error when saying 'exit'

No 'Unhandled' function defined for event: Unhandled

You can add this intent to your handler to capture exit and clean up any sessions:

'SessionEndedRequest': function () {
  console.log('session ended!');
 }

[TDA]

@JennJin I see that you have closed a bunch of issues today, is there an official way to handle this? I would like to see a response from the core team on what the right way to solve this is, before closing it out.

[TDA]

@JennJin Thanks for the detailed explanation :) That is pretty much what I expected, it appears that the certification team isn't caught up with that yet. I will continue the discussion on the forums. Thank you!

[Shivam-Singh-02]

Hey Guys that's a very genuine question. I figured out if you add "SessionEndedRequest" intent before your "LaunchRequest" intent(You can put it anywhere though) and inside it just have "this.emit(':responseReady')" and nothing else. Works fine.