Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swift Demo Project #21

Open
grantkemp opened this issue Jan 2, 2017 · 2 comments
Open

Swift Demo Project #21

grantkemp opened this issue Jan 2, 2017 · 2 comments

Comments

@grantkemp
Copy link

When attempting to use the "Voice Button Request" nothing happens and there is an error logged into console:

2017-01-02 01:45:02.102002 ApiAIDemoSwift[917:151587] [] nw_endpoint_handler_add_write_request [1.1 52.222.241.69:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:02.102678 ApiAIDemoSwift[917:151588] [] __tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-01-02 01:45:06.285527 ApiAIDemoSwift[917:151589] [] nw_endpoint_handler_add_write_request [2.1 52.222.241.69:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:06.286643 ApiAIDemoSwift[917:151589] [] nw_endpoint_handler_add_write_request [2.1 52.222.241.69:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:06.288061 ApiAIDemoSwift[917:151586] [] __tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument```

Assuming Voice has been deprecated - it might be useful to remove `Voice button Request` from demo
@grantkemp
Copy link
Author

grantkemp commented Jan 5, 2017

From further testing it seems that different Client Keys perform differently

  • let clientkey_APIAi = "b316a120a0ab4383980746032c21c4f5" // This one from the github sourcecode seems to work pretty consistently.
  • let clientkey_APIAi = "d915ba7bf4e842af9b7cc2c6ebf1a686" // This test one that I generated recently seems to fail 100%

Is there a setting/ difference in these codes which can result in the Voice recognition not returning any data . How can we get newly generated keys to perform as well as the older client keys.

@allenelks
Copy link

I'm having the same issue. The requestVoice() API method is still listed in the README.md as a valid option, but this appears to be broken on IOS (Android is working just fine). Can we get official word on this as a viable option? If anyone has a solution for IOS, I'd greatly appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants