Closed favna closed 6 years ago
Hi @Favna ,
Before digging any further, can you test a simple res.say
in your CardResponses branch?
The SkillDebugger log you attached showing there was no response from your lambda function, so I just want to verify whether this is a framework (bad card format) or a setup (restricted lambda) issue.
Also, if you can mention your Lambda node.js version, it can help too.
@kobim res.say
works just fine, both in my CardResponses branch and master branch. My Lambda is on Node 6.10, I've trying to make that go to Node 8.11.2 but everytime I do an apex deploy
it is set back 🤔
I made a lot of adjustments to the code as Amazon got back to me for my skill verification and thus I have updated the URL of the code part of card stuff on the original post but just for good measure, here it is as well.
The card code is now commented out, but it is otherwise unchanged since the original post and the issue persists.
Try using type: 'Simple'
(upper case first letter) and not lower-case simple.
(it took me a while to notice that)
Oh wow that did it. I didn't notice that at all either. Thanks!
For my skill I'd like to have both a spoken response as well as a card response so people can view the data again later in the app, however whenever I add my
response.card
Alexa throwsThere was a problem with the skill's response
without any indication of what the error is. There is also no indication of what the error is on Lambda and the exact same input works just fine when only having aresponse.say
.AWS logs:
Code can be seen in my CardResponses branch (currently only the DexIntent file):
https://bitbucket.org/Favna/dexa/src/CardResponses/functions/dexa/intents/dexintent.js#lines-126
When logging the response in manual mocha tests it does seem to be a-ok when comparing it to what Amazon has in their docs (barring that their example doesn't have SSML but Plain Text for the outputSpeechType)
Some Semantic stuff