Bad debugging
When I get the "There was a problem with the request3d skill's response" reply it would be 1000% more helpful if you would at least display what the response was even if you cannot tell me what was wrong with the response
Anonymous
shared this idea
-
Palmieri Matteo
commented
Totally agree with the request of having endpoint response dumped in the skill tester log. There are cases when the skill code is deployed on a backend, not a lambda and you don't have access to backend logs. Having both request and response available in the skill tester log would speed up troubleshooting.
-
Evgeni Nabokov
commented
You can reproduce the request in the Test console, then mark the checkbox "Device log" and carefully read the JSON log entries. Usually you will find a message with specific error. It works not in 100% of cases, because sometimes I get Internal Service Error without an explanation.
-
Brian R Campbell
commented
Setup your local environment for debugging and then you can look at the error when it happens...this document tells you how
http://microdesigncentre.com/setting-up-a-local-alexa-skill-development-environment/ -
Alexandre Blin
commented
@Ron Wang: this doesn't work if you're using your own web server to handle the requests
-
Ron Wang
commented
This can be a bit mitigated by using ask-cli. https://www.npmjs.com/package/ask-cli.
If you use ask-cli, like the "ask dialog" command to simulate with you developed skill, and if this message happens, you can run "ask lambda log" to immediately retrieve the recent cloudwatch logs, and you can very likely see the reason why this request failed. Hope this will help!
-
Cole Orton
commented
Totally agree.