Updating to XCode 26.2 and macOS Tahoe 26.2 and im now greeted with "Trace file had no swiftui data" this occurs if I profile with XCode and chose a template I profile with XCode and chose a blank template and manually choose SwiftUI I manually run the Instruments, manually run the app, attach and open a document in my swiftUI app however, if i DO NOT load a document (macOS based swiftui app), im able to get swiftui traces my feeling here is theres something going on with complicated traces that cause an issue modelling the data stream, or capturing the trace? Im not familiar with the nuances here but this isnt working for anything that NEEDS profiling.

Hello Im having similar issues, however with Instrumenting a macOS application. Instruments + SwiftUI was working great with XCode 16.3 and macOS 15.5 I recently updated to macOS 15.7.2 and XCode 26.1.1 And now When I run my application via Product -> Profile (Command I) SwiftUI Template Run Instruments launches my app for a microsecond, and then fails with Failed to start the recording: Failed starting ktrace session. Some notes For my macOS target, i can only choose deferred mode for the Recorder Settings

hi. Ive looked at that sample, and while I could refactor my drawing code to use CALayers, it's really not pertinent given my current pipeline. Are the attributes for background simply not supported in TextKit 2?

Its 2025 how is it possible that the most modern text rendering framework in macOS has undocumented coordinate systems backgrounds dont draw right Genuinely asking here.

Can I ask a dumb question? Is there a reason you need to customize the decoding of an HLS stream yourself? Does your stream work with AVURLAsset -> url of HLS playlist -> AVPlayer? Just curious! As for the error, are you certain you are vending samples to the decoder in DTS order, and that your CMSampleBuffers contain Block Buffers with fully demarcated NAL units, sync info and extra data? I dont know how to resolve your issue specifically to be honest, but ive absolutely seen that not fully setup sample buffers can cause the decoder to fail in unexpected ways.

You need to ensure that you re-use tracks in your composition when creating a composition. Validate that your existing composition video track can be re-used when making a new insert / edit - assuming you dont need multiple tracks for transition effects. The API for this is mutableTrack(compatibleWith track: AVAssetTrack) -> AVMutableCompositionTrack? The way this works is for every source video track you want to edit into your composition: check if there is an existing compatible track on your composition if there is, use it if not, make a new one and use that, The more times you can re-use the same track (ie for standard edits) the better, and less memory you will consume.

And note, that video with the same / compatible CMFormatDesc should allow for track re-use. If you happen to have 42 videos with completely incompatible formats (ie resolution, frame rate, pixel format, color space) are all unique combinations, you will get zero re-use. if all videos are say, 1080p 30, BGRA rec 709 you should get 100% re-use.

FWIW, quitting Xcode and purging the folders mentioned by @SubvertDev allowed me to resolve the package dependency error. Im on Xcode 16 on macOS 14.5, and had the error in a fairly large Xcode Project with lots of dependencies.

I was able to get a key frame decoded by ensuring I properly populate the extra data for the CMFormatDescription, but have yet to get GOP frames working.

Ah, so this appears fixed in macOS 15. Older Virtualization Framework systems (ie older hosts) won't work. https://developer.apple.com/documentation/virtualization/using_icloud_with_macos_virtual_machines Can we get confirmation that: macOS 14 (13, 12, 11 etc) running as a guest on a macOS 15 workstation would get a Secure Enclave identity allowing the macOS 14 (13, 12, 11 etc) guest OS to sign into iCloud, use Xcode, etc?

This really needs to be resolved. The ability to test, debug, and build apps in professional workflows requires ease of setting up VMs and debugging apps. Xcode requires Apple ID login, which does not work in a VM like UTM. This means I can't easily debug my software on new OS'es without updating my entire system? Thats insane in 2024 with containerized workflows as a defacto standard. Come on.

I haven't had a chance to test my vanilla m1 for performance numbers, but it seems like macOS 12.3 has fixed the H11ANEDevice::H11ANEDeviceOpen kH11ANEUserClientCommand_DeviceOpen call failed result=0xe00002bc error I have also been getting on M1 Pro / M1 Max systems.