Daniel (dB.) Doubrovkine

Personally I'd side with @OverloadUT around unnecessary trapping of errors, I ran into this problem a million times while developing a skill. Maybe @OverloadUT can propose a pull request that...

Philosophically I think those should have the same level of support inside this library - what I mean is that if we have code that helps with lambda in alexa-app...

I want to add that right now on HEAD we went almost the other direction. There's a bunch new code to make it work in the Express scenario and to...

I would examine the JSON/SSML that comes out of this function and see if all the parts are there for a start.

Just use `curl` against your local web service. If you're using lambda you can use `apex`. I talked about both of those in http://artsy.github.io/blog/2016/11/30/bringing-artsy-to-amazon-echo-alexa/, that could be helpful. Also maybe...

If you're talking about the test UI I bet it's not supported, those were *just* added in https://github.com/alexa-js/alexa-app/pull/92. So `curl` and friends. But would appreciate PRs for anything that helps...

@fremail Thanks! I think we could throw an error when you try to do both audioplayer and `say`, couldn't we? I see a nice PR opportunity here ...

Right. Would you at least open an issue on the latter @fremail? Thx.

Thanks @fremail, all we need now is a fix ;)

So... aside of exceptions, do we need to throw an error inside audioplayer requests when we do `say`?