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.
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.
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.
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.