After upgrading to iOS 18.4, I noticed that launching a debug build from Xcode becomes extremely slow. The same app with the same large debug binary (~1GB) launches normally on devices running iOS 18.3. This issue seems specific to iOS 18.4, possibly related to the way the OS handles large debug binaries or symbols during the launch process. Steps to Reproduce: Connect an iPhone running iOS 18.4 to a Mac with Xcode. Build and run an app using Xcode in Debug mode. Observe the extended launch time. Re-run the same process on another iPhone with iOS 18.3 — launch is fast. Expected Result: Debug launch should be fast and consistent across iOS versions. Actual Result: Debug launch is significantly slower on iOS 18.4 for large binaries (~1GB). Environment: Xcode version: 16.0 macOS version: 15.4 Device: iPhone [model] iOS version: 18.4 (problematic), 18.3 (no issue)

Hi, When I use Xcode to build, It will generate xcactivitylog. But When I use xcodebuild, For example xcodebuild -workspace xx.xcworkspace -scheme xx -sdk iphoneos -showBuildTimingSummary -resultBundlePath ./a/a -derivedDataPath ./a clean build it will generate two xcactivitylog, One is a clean job log, and one is a build job log. But the build job log is not a valid gzip. I have to wait one day, but nothing changes. So, Is it possible to crash in generate xcactivitylog？ If I use hmap to replace the header search path, it works fine. So I think it may be argument too long lead to generating log failed. One more thing, it only failed in a large Xcode project.