It's still happening in iOS 16. Not even fixed in iOS 16

Also in your code, if the autorelasepool error occurs after the stop call, it crashes at the "synthesizer = nil" location and the app dies.

Currently, when AVSpeechSynthesizer stop is continuously performed on iOS 16 or later devices, the AVSpeechSynthesizer object is released, resulting in an error or loss of voice control and reading to the end of the current sentence. So I was wondering if there is any other way other than using the function of AVSpeechSynthesizer .

Both stopSpeaking(at: .word) or stopSpeaking(at: .immediate) won't stop after stopping the AVSpeechSynthesizer if an error occurs and the voice playback control is lost. Also use word or immediate to stop the current playback before the AVSpeechSynthesizer error.

We are currently uploading this issue through the Feedback app (installed on beta iOS versions). Feedback ID is FB11711356. We are waiting because this issue affects the apps we sell. Could you please let me know if this issue or feedback is ongoing or what is going on? If the iOS issue is correct and can be improved, we will try to answer that users will improve it with an iOS update when they inquire about the problem.

If you want to quickly check the symptoms when testing additionally, when tapping, instead of tapping your finger on the screen immediately after tapping, tap the screen a little later and move to the next page to reproduce the symptoms more quickly.

I just checked the iOS 16.1 beta after updating my iPad Pro 12.9 2nd generation device. It appears that this bug remains unfixed in iOS 16.1. Please check the iOS 16.1 beta version as well.

Please reply after checking the file. (The cause or if it can be improved in the next iOS update) Be sure to test on an iPhone 14 Pro or iPhone 14 Pro Max. (Simulation is not recommended.)

We shared the sample code compressed file as a Google Drive link. : https://drive.google.com/file/d/142_ymW1CGnOwIcYU7SWnR_3JAhxUPQYG/view?usp=sharing

I'm trying to add this code to my app in the next update, but the crash still comes? @available(iOS, introduced: 15.7, obsoleted: 16.0) @objc extension SKStoreProductViewController { func sceneDisconnected(_ arg: AnyObject) { } func appWillTerminate() { } }

Added code on TTS generation and exit.

Thank you for answer. When testing using StoreKit, closing the app in the background actually causes the app to crash. However, since it occurs in the background, it may have little effect when users use the app. But if we want to reduce those crash logs, we should use extenstion on devices after iOS 15.7.

I've replied back below. please note

It seems to be caused by the AdMob library, so I posted the issue to the AdMob community. If I get a solution answer or find a solution, I'll upload it.

We've been working on putting 20000 ViewControllers into an Array. We've seen that putting 20000 into an Array using append() doesn't take much time. However, it took a long time when I called removeAll() to delete the previously inserted 20000. It took about 15-20 seconds between calling removeAll and completing all append . We've even seen that using [] instead of removeAll() is time consuming which doesn't make much difference.