Speech Recognition Problem in iOS 18.0

App & System Services General Speech

Created Aug ’24

Replies 35

Boosts 8

Views 3.1k

Participants 16

It looks like Apple has added some new API(s) to SFSpeechRecognition My app, which is currently listed on App Store does feature speech recognition. Yet, trying to use it under iOS 18.0 throws errors: -[SFSpeechRecognitionTask localSpeechRecognitionClient:speechRecordingDidFail:]_block_invoke Ignoring subsequent local speech recording error: Error Domain=kAFAssistantErrorDomain Code=1101 "(null)" What happens is that after several words are transcribed and displayed, the next sentence results in previous words disappearance. That's probably what that portion of the error text - "Ignoring subsequent local speech recording error: Error Domain=kAFAssistantErrorDomain Code=1101 "(null)" means. The problem occurs ONLY when the app is running under iOS 18.0 Even when it's compiled in Xcode 16.0 using iOS 17.5 everything works fine. Any suggestions?

Boost

righteoustales OP

Oct ’24

Also, I forgot to mention above. The bug resolution also had:

Recent Similar Reports:None

This despite the fact that my written description explicitly included this verbiage:

Other reports of this bug are here: https://forums.developer.apple.com/forums/thread/762952 https://forums.developer.apple.com/forums/thread/731761

iaborodin OP

Oct ’24

@righteoustales No reply for me either. Apparently, this bug has low priority. Nevertheless, it would be a matter of curtesy if not respect on the part of Apple toward developers (respect, by the way, they swear on all the time) to at least drop a line informing that the report(s) are on the backlog and will be looked at when the time permits.

Squids OP

Oct ’24

I haven't gotten a reply on my report either. But I'm seeing the behavior on the developer 18.1 beta has reverted back to the pre 18.0 behavior.

I'm worried that solutions to this bug could give users an inconsistent experience if/when they update to 18.1

ehrpaulhardt OP

Oct ’24

Same here: FB15555684

jasonh9 OP

Same same, different place, same bug

FB15587171