Nothing came back Issue

[abhijagtap73]

Hi, thanks you for your code, actually i am testing app with alexa skill set, it working fine but some time frequently it gives Nothing came back error, and take too long time from record.start(); to request body, is there any way to call alexa request synchronously for efficient result. can you share synchronous alexa request and response.

[vkreal]

I am also seeing some lag time. Anyone have any ideas to fix them? Maybe doing the processing in C++ Native will help?

[KushtrimPacaj]

This is happening to me also, but haven't had time to try and debug. If anyone has any ideas, I'm up for help on implementing.

[KushtrimPacaj]

@willblaschko This is happening way to often to me, and I haven't had any luck debugging. I don't really know where to start the debugging. Any ideas why Amazon returns 204 sometimes ?

[willblaschko]

204 can come back for several reasons:

• The main one is to show that it received an event (this is supposed to happen)
• It didn't understand what the user said (this is annoying)

Usually it is supposed to happen.

[ihavenoface5]

I have found that the majority of 204 errors come from a poor recording. It was helpful for me to save a recording and play it back.

[syedtalha]

Is it supposed to be a phone specific issue or a network specific issue?

[KushtrimPacaj]

@willblaschko Regarding your comment ("The main one is to show that it received an event (this is supposed to happen"), do you mean that it returns 204 like an acknowledgment ? How it would then receive the response?

I usually test it with the word "Weather", and while normally it tells the weather, sometimes it always returns 204 no matter what I do ( whether I am close, far, speaking slowly or not ),

[KushtrimPacaj]

@willblaschko I saved the bytes we're sending to the server to a file, and then tried sending the same file. When I sent a file of a recording for which the server had returned 204, it always returned 204 for that file. Same for a recording for which the server had returned a response, it always returned a good response. This means that it's really an issue with the server not understanding what was said in the recording, and not a fault of the library itself.