Closed duncsand closed 8 years ago
I now am also receiving this bug.
@daniel-bolanos do you have an idea of what this is ?
I have an idea what mitt be causing it after some testing. Could be invalid json inbound. I'm going to try with some escaping of the question text and see if that works.
Sent from my Verizon Wireless 4G LTE smartphone
-------- Original message -------- From: German Attanasio Ruiz notifications@github.com Date: 10/12/2015 10:14 AM (GMT-05:00) To: watson-developer-cloud/speech-ios-sdk speech-ios-sdk@noreply.github.com Cc: scprotz scprotz@hotmail.com Subject: Re: [speech-ios-sdk] random "This doesn't look like a Opus file" error (#8)
@daniel-bolanos do you have an idea of what this is ?
Reply to this email directly or view it on GitHub: https://github.com/watson-developer-cloud/speech-ios-sdk/issues/8#issuecomment-147410302
I found out what was causing the issue. I was using my Bluemix login credentials to authenticate using basic auth. When I replaced those with the TTS Bluemix Service credentials shown in the Bluemix dashboard for the TSS service I'd provisioned, everything works fine.
Using incorrect credentials should generate a clear error message at the SDK level, so I think there's still a bug to fix here. (Renaming this issue to reflect that.)
I get random "This doesn't look like a Opus file" errors when using text-to-speech. They seem to be based on the contents of the text being passed in. For example, "Welcome to your watson virtual assistant" gets an error, whereas "Welcome to your virtual assistant" works fine. The errors appear to be coming from OpusHelper.m This is on iOS9.