Speech recognition started and immediately failed with kAFAssistantErrorDomain error 7

Question

Created Oct ’20

Replies 5

Boosts 0

Views 1.9k

Participants 6

Some details:
iOS14.0.1
Xcode 12.0.1
iPad Mini gen 5

Our app uses voice as the main user input to navigate the functionalities.

Upon app start, speech recognition works normally. The user would start saying simple English words (Yes/No), and the speech recognizer would start hypothesizing transcription.

However, after a few iterations, the speech recognizer would stop working. Instead of hypothesizing transcription when user speaks, it jumps straight to the didFinish task delegate and indicates that speech transcription was unsuccessful with the following error message: The operation couldn’t be completed. (kAFAssistantErrorDomain error 7.)

This bug only appeared recently in iOS14 and was not an issue in iOS13. I have googled for this error code/message but could not find much detail. Does any one know what this means/why it is failing?

Boost

Answer 1

michaelfromwest bloomfield OP

Nov ’20

I’m also facing this issue, any solutions or new discoveries?

0

Answer 2

jesso.a OP

Jan ’21

The same!

0

Answer 3

jlajlar OP

Feb ’21

I'm having the same difficulty as described in the original question. The documentation for SFSpeechRecognizer says that each app has limited number of requests it can make, so I'm guessing this is the case.

Be prepared to handle failures caused by speech recognition limits. Because speech recognition is a network-based service, limits are enforced so that the service can remain freely available to all apps. Individual devices may be limited in the number of recognitions that can be performed per day, and each app may be throttled globally based on the number of requests it makes per day. If a recognition request fails quickly (within a second or two of starting), check to see if the recognition service became unavailable. If it is, you may want to ask users to try again later.

What's interesting is that when I check isAvailable flag on speech recognizer instance, it returns true. Also, there's no way to recover from this error. I've tried reinitializing speech recognizer instance, canceling the request/task, but nothing works. What I found out is that only killing the app recovers from this error.

0

Answer 4

cypher OP

Apr ’21

I am also seeing this. I'm going to experiment with turning on recognitionRequest.requiresOnDeviceRecognition as it has nothing to do with those network services, so presumably removes these limits.

0

Answer 5

AliakseiKartashou OP

Nov ’23

Facing the same issue any updates on workaround/soluton?

0