Yes, it's a good idea! I submitted a feedback (FB24876852).

💡 There's an explanation in this thread: https://developer.apple.com/forums/thread/844711

Oh, I see. My MacBook is from China (Z1FQ000DMCH/A), which explains why I can't turn on the Apple Intelligence option, unfortunately. Thank you very much for your explanation 🙏

There is no any agent component, only Metal Toolchain and Developer Documentation ☹️

Which version of Swift do you use?

I'd like to clarify: are you sure that you're using the async/await API specifically? At one point during my research, I thought I had fixed the crash by using this API, but I was mistaken. Here is the code I wrote: func setAppIcon(with name: String?) { UIApplication.shared.setAlternateIconName(name) } In fact, I was actually using the API with a completion block.

We use Fastlane in our CI system. Therefore, we've replaced all the methods that we used and that had the xcodebuild_formatter argument.

I returned with my feedback. Initially, my issue wasn’t with local builds, but rather with our CI system. However, I had overlooked this detail. The problem was actually with the xcodebuild formatter that Fastlane uses. By simply changing xcpretty to xcbeautify, I resolved the issue, and our compile timings returned to being acceptable for us 😎

Yes, the problem still exists in my project. However, I can't say that it's some major concern for me, but I'd like to utilize more convenient method that works in iOS 17+. In addition, it's very curious why the API doesn't work well in iOS 16.