Critical BUG! Could you fix it asap or at least set the try/catch block with the reporting via NSError or somehow else?

Crashed: com.apple.TextToSpeech.SpeechThread 0 libobjc.A.dylib 0x3518 objc_release + 16 1 libobjc.A.dylib 0x3518 objc_release_x0 + 16 2 libobjc.A.dylib 0x15d8 AutoreleasePoolPage::releaseUntil(objc_object**) + 196 3 libobjc.A.dylib 0x4f40 objc_autoreleasePoolPop + 256 4 libobjc.A.dylib 0x329dc objc_tls_direct_base<AutoreleasePoolPage*, (tls_key)3, AutoreleasePoolPage::HotPageDealloc>::dtor_(void*) + 168 5 libsystem_pthread.dylib 0x1bd8 _pthread_tsd_cleanup + 620 6 libsystem_pthread.dylib 0x4674 _pthread_exit + 84 7 libsystem_pthread.dylib 0x16d8 _pthread_start + 160 8 libsystem_pthread.dylib 0xba4 thread_start + 8

That's a message for Apple, not for the developers forum.

If not done yet, you should file a bug report.

Hello, please attach a sample project and any relevant crash logs in a bug report using Feedback Assistant, this will help immensely with triaging and debugging the issue you are encountering. https://developer.apple.com/bug-reporting/

If you have done so already, please share the feedback ID number so I can make sure the right folks see your report. Thanks!

I am currently having similar symptoms. When I repeatedly play and pause using AVSpeechSynthesizer, I get that error right away. If you look at the forum posts, it seems that this error has occurred since the iOS 16 beta. However, it seems that Apple hasn't fixed this error yet. I have the same error on iOS 16.2 beta devices. I'm waiting for Apple to fix this issue when it finds out, because symptoms can easily come out by making a sample code and testing it a little. Or, wait for the news that Apple is preparing to release iOS 16.1.1.

private var synthesizer: AVSpeechSynthesizer? this is my variable. i have in deinit:   deinit {

       synthesizer?.delegate = nil

       synthesizer = nil

    }

when i comment synthesizer = nil crash app not crashed

Critical BUG! Could you fix it asap or at least set the try/catch block with the reporting via NSError or somehow else?
 
 
Q