A Summary of the WWDC25 Group Lab

Through trial and error I have found what causes this issue (at least one cause.- maybe there are more). The problem for me was caused by the combination of two things: Having the Blur option switched on for one of the groups in the Icon Composer file For that group, having at least one SVG sitting near the edge of the canvas. I'm not sure exactly where the line is, but if your SVG is in the middle, it doesn't trigger the issue - even with Blur turned on. It only shows up once your SVG is near the edge. So for me, the fix was to turn off the blur setting on the group that had an SVG near the edge.

auval -a shows me following: auval -a AU Validation Tool Version: 1.10.0 Copyright 2003-2019, Apple Inc. All Rights Reserved. Specify -h (-help) for command options aufx bpas appl - Apple: AUBandpass aufx dcmp appl - Apple: AUDynamicsProcessor aufx dely appl - Apple: AUDelay aufx dist appl - Apple: AUDistortion aufx filt appl - Apple: AUFilter aufx greq appl - Apple: AUGraphicEQ aufx hpas appl - Apple: AUHipass aufx hshf appl - Apple: AUHighShelfFilter aufx lmtr appl - Apple: AUPeakLimiter aufx lpas appl - Apple: AULowpass aufx lshf appl - Apple: AULowShelfFilter aufx mcmp appl - Apple: AUMultibandCompressor aufx mrev appl - Apple: AUMatrixReverb aufx nbeq appl - Apple: AUNBandEQ aufx nsnd appl - Apple: AUNetSend aufx nutp appl - Apple: AUNewPitch aufx pmeq appl - Apple: AUParametricEQ aufx raac appl - Apple: AURoundTripAAC aufx rogr appl - Apple: AURogerBeep aufx rvb2 appl - Apple: AUReverb2 aufx sdly appl - Apple: AUSampleDelay aufx tmpt appl - Apple: AUPitch aufx vois appl - Apple: AUSoundIsolation aumf Al

Hello, Quartz Debug is available as an additional tools package for Xcode. For example, Additional Tools for Xcode 26 beta 6 contains: This package includes audio, graphics, hardware I/O, and other auxiliary tools. These tools include AU Lab, OpenGL Driver Monitor, OpenGL Profiler, Pixie, Quartz Debug, CarPlay Simulator, HomeKit Accessory Simulator, IO Registry Explorer, Network Link Conditioner, PacketLogger, Printer Simulator, 64BitConversion, Clipboard Viewer, Crash Reporter Prefs, Dictionary Development Kit, Help Indexer, and Modem Scripts.

Nothing I can say for sure unfortunately. The error message seems to indicate that the model container was changed and so the model context lost the link to a back store. (That can't explain why accessing title is fine however.) You can probably try with creating a (singleton) model container shared across the whole app and passing it to your window group with .modelContainer(sharedModelContainer) to see if that changes anything. Best, —— Ziqiao Chen  Worldwide Developer Relations.

FWIW, I'm getting this on Xcode 16.4 with no Swift Package Manager. The error alert will popup in groups of 5 or 6. All the buttons just close the alert and lead to another one.

I decided to run this task on app launch to sync the clinical labs into the SwiftData store. This allows me to use Query macro in the views where it's needed and no need to combine lab results. Let me know if this is the right approach: import SwiftData import SwiftUI import OSLog @ModelActor actor HealthKitSyncManager { private let logger = Logger(subsystem: com.trtmanager, category: HealthKitSyncManager) func sync() async { do { // Get all Clinical labs let hkClinicalRecords = try await TRTHealthKitService.getHKClinicalRecords() guard !hkClinicalRecords.isEmpty else { return } // Get existing HealthKit IDs in one query let descriptor = FetchDescriptor( // predicate: #Predicate { $0.source == .clinicalRecord } ) let existing = try modelContext.fetch(descriptor) .compactMap { $0.fhirResourceId } let existingIDs = Set(existing) let missingRecords = hkClinicalRecords.filter { lab in guard let fhirResource = lab.fhirResource else { return false } return !existingIDs.contains(f

It's unclear what LabResultDto in the code snippet is. If it is a Sendable type that wraps the data in a SwiftData model, that's fine; if it is a SwiftData model type, because a SwiftData model object is not Sendable, you won't want to pass it across actors – Otherwise, Swift 6 compiler will give you an error. For more information about this topic, see the discussion here. When using SwiftData + SwiftUI, I typically use @Query to create a result set for a view. Under the hood (of @Query), the query controller should be able to detect the changes you made from within a model actor, and trigger a SwiftUI update. Fore more information about observing SwiftData changes, see this WWDC25 video. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hi @DTS Engineer We attempted to capture a fresh sysdiagnose, but we were unable to reproduce the issue in our lab. We will continue our efforts to replicate the problem. [quote='852684022, DTS Engineer, /thread/783870?answerId=852684022#852684022'] PushKit and CallKit should both be configured in applicationDidFinishLaunching. The goal here is that you want CallKit to be fully configured before your PushKit delegate is called to deliver a VoIP push. I would add an additional call to set the configuration before you call reportNewIncomingCall on the first push you receive, as this should ensure that callservicesd has a valid session ID. Note the configuration doesn't need to change, so setting the configuration to the existing value will work fine. [/quote] I believe our app shall have done this correctly, as both incoming and outgoing calls functioned properly before the problem occurred. Our application did not restart or reinitialize during this time. The issue does not happen on the first call(pu

Hello! The test report has received an overhaul as of Xcode 15. When you open your result bundle in your workspace, you'll be able to find the jump buttons to navigate to the source code in the test case details screen. To get to the test case details screen, you can double click on the corresponding failed test on the Summary screen, or by double clicking into the test in the Tests Outline screen. On either the activities tab or the runs tab, the jump button will appear when you hover over the callstack row. You can also navigate to the source by clicking on the View Source button in the header of the test case details screen. See the WWDC23 video Fix Failures Faster for a tour of the test report - https://developer.apple.com/videos/play/wwdc2023/10175/