Also cannot figure this out. This feature is not useful for my apps without Catalyst support

I figured it out. I just found this: https://developer.apple.com/documentation/appintents/audioplaybackintent

The memory leak that I was seeing seems to be fixed in iOS 17 but it still has performance issues. For example, it doesn't stop speaking immediately when you call stop(.immediate)

This seems to be fixed in the iOS 17 beta

I just figured it out. You must declare the parameter as coreimage::group::destination dest

@shaharbd Thanks for excellent reply! You've given me much to look into here! I appreciate it.

I have a workaround for this bug that seems to work. Sharing it in hopes of helping others... So it seems this bad behavior occurs (in my case anyway) when you wrap a NavigationView with other custom UI. In my case I had a custom tab bar view which wrapped a NavigationView. Sometimes the content inside the NavigationView would become completely unresponsive to user interaction but the custom tab bar would remain functional. Now for the workaround: I found that if I set the custom tab bar view to disabled(true) then focus would be forced to change back to the NavigationView. So a workaround would be to temporarily disable all of the custom UI surrounding the NavigationView then re-enable it. You'd have to get creative with making this work reliably--something like a periodic async timer that enables/disables stuff. I'm still figuring out the best solution for my app. Just thought I'd share.

Hello Frameworks Engineer . Is there an update on this?

Thanks for the response. A test project demonstrating the pitch issue is attached to FB9097088

I'm seeing this issue now. Nothing in my codebase changed. I regret adopting this API

@ibatis Still crashing on my iPhone but it no longer crashes in the simulator. I guess it will take some time for devices to download the updated file(s).

It is an asset issue though so an OTA update should resolve this without an app update required from any developer. Any idea when the update will be available? My app depends on this functionality.

OP, is this the same crash you are seeing? looks the same, yes. it seems to be limited to iOS 14.2+ but I also just started hearing reports about it early on the 20th.

Can you share the feedback ID that you filed? Thank you for the reply. Feedback ID is FB8976882. I've reproduced this bug on several iOS devices and simulators using 14.2, 14.3 and 14.4 beta.

Yes I'm seeing this also. Just posted a similar question. This kind of stuff seems to be even worse in my SwiftUI apps. Would love an explanation.