Scott

This is happening to me as well on Android (not tested on iOS). During partial results sometimes you have higher confidence later in the array list (which I would've assumed...

@chris-rudmin it looks like you axed the WAV stuff out of this. Sadly I would love to use a compressed format, but the voice engine requires 16kHz, 16bit, mono WAV...

@complanboy2 --- I'm sorry for not seeing this until now. Since this was 3 years ago, I honestly don't remember what I ended up doing. https://developer.mozilla.org/en-US/docs/Web/API/AudioBuffer is the current way...

This looks like another example of this: https://github.com/endoplasmic/google-assistant/issues/42 The audio comes back correctly, but because it requires a followup, it seems like the response text is blank.

Just to follow up. If you type "any flower shops near" it *does* work, but "nearby" doesn't. So odd.

What is the Firebase app doing in this scenario? It seems like it's missing some sort of configuration? I just tried the example and it seems to be working fine...

I know this is a bit old, but did you end up figuring out your issue @Roaders?

I'm actually seeing a different error on my end altogether... I don't see any changes to the proto files on google's end, so I'm wondering if whatever happens after the...

For traffic I seem to be getting text: ``` Type your request: What's the traffic like to work? Assistant Response: On your way to work, traffic is light, as usual....

I'm seeing the same on my end regarding traffic. Blank text response. Sounds like a bug in the SDK. If you wanted to you could always take the audio as...