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 😎
Amer1go
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
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.