Hi there, How to let instruments - app launch template wait for process to launch , rather than actively launch by instruments? I need to profile the app launch performance when clicking a push notification or cold launch via a url link. How to let instruments to wait for the process and collect the data? Currently, I tried the command xctrace record --template "App Launch" --attach MyApp --device-name 'Phone-Dev' --output mytrace.trace But it soon failed with 'Cannot find process matching name: MyApp'. How to make it work?

So we are testing our app code base with Xcode16 and fix any compile errors. After it builds and run, we found our tar bar controller's tar bar is behind the selected VC's view. We thought it is our bug, but we have tested below combo: Xcode15 + iOS18 - Fine we are invited to your office to test the new iPhone 16 series, they are iOS18, and our app on the app store is totally fine (built with Xcode 15) Xcode15 + iOS < 18 - Fine Apparentely ok, it's shipped. Xcode16 RC + iOS 17 device - Fine it's also fine Xcode16 RC + iOS18 RC: tar bar is behind selected VC because we are not able to add iPhone 16 model to our account, we flushed our in-house device to iOS18 RC to test Xcode16 built app, The tar bar is behind the selected VC. We want to ask for help ASAP because we are totally out of mind what's going on. I have filed FB 15120641 but want to raise it here to gain more support and insights.

Xcode beta 5 still compile failures around method having label of module our method like (nullable NSDictionary<NSString *, NSString *> *)strategyWithBusiness:(NSString *)business module:(NSString *)module config:(NSString *)config; filed bug: https://feedbackassistant.apple.com/feedback/14712382 seems other also reports this, but I would like to raise for xcode beta 5, still not fixed.

Hi there, I already filed radar FB9958917 two weeks ago and no response. this is super annoying when you are debuging a giant app and suddenly you switch the input source, and all debug work is gone and I have to kill xcode to start over again. unacceptable, only happens after you upgrade to 13.3