Swift 6

Do you have a full symbolicated crash report to share? You can include crash reports directly in your post using the forums attachment feature. For any random crash related to SwiftData / Core Data, I'd suggest that you add com.apple.CoreData.ConcurrencyDebug 1 as a launch argument of the app to check if there is any violation, as discussed here. Also, I guess ConsumptionSession is Sendable? Otherwise, Xcode will give you an error if you compile with Swift 6. If you haven't used Swift 6, I'd suggest that you give it a try to see if that unveils any race condition. Best, —— Ziqiao Chen  Worldwide Developer Relations.

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.

What you observed is the behavior that the framework currently has – If you save the model context right after adding a book, you will see that the relationship turns from nil to [] immediately, and that's because SwiftData makes the change when persisting the model. SwiftData does that because the default store (DefaultStore) is based on Core Data, and Core Data expresses an empty toMany relationship with an empty set. (Core Data had been implemented with Objective C long before Swift was introduced.) Having said that, if you have a different opinion about the behavior, feel free to file a feedback report – If you do so, please share your report ID here. Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I’m also seeing this issue on my end. In our app we use Swift Charts inside a ScrollView, with simultaneous gestures applied in the chart’s overlay block (for interactions like drag/tap on data points). Since iOS 26 beta 1, this completely breaks the parent ScrollView’s vertical scrolling. This was never a problem on iOS 18, the exact same code works fine there. I also noticed that the release notes for beta 5 and beta 6 mention fixes for simultaneousGesture conflicts in scroll views, but this bug is still reproducible. So unfortunately, it’s not fixed yet, and I haven’t found a workaround so far.

Step 6 - Get a digital identity from the keychain: private func getClientIdentity() -> SecIdentity? { let query: [String: Any] = [ kSecClass as String: kSecClassIdentity, kSecAttrLabel as String: MTLSTag.clientcert, // <-- match by certificate tag kSecReturnRef as String: true, kSecMatchLimit as String: kSecMatchLimitOne ] var identityRef: CFTypeRef? let status = SecItemCopyMatching(query as CFDictionary, &identityRef) if status == errSecSuccess, let identity = identityRef as! SecIdentity? { print(Retrieved client identity from Keychain) return identity } else { print(Could not retrieve client identity, status=(status)) return nil } } Usages : func updateCertificates() { // Load CA certificates (if needed for server trust validation) self.trustedCACerts = CertificateUtils.getCACertificates() self.storeCertificatesInKeychain() if let useridentity = self.getClientIdentity() { self.clientCredential = URLCredential(identity: useridentity, certificates: nil, persistence: .forSession) } }

Hello, Thank you for sharing the provided solution. I followed all the steps and used the same API set. However, while retrieving the SecIdentity using the certificate fetch API SecItemCopyMatching, I am encountering the following error: Error: Could not retrieve client identity, status = -25300 Please find the relevant code snippets below: Step 1 to 3 : Generate the private key in the keychain. Derive the public key from the private key. Export the public key bits and send that your certificate issuing infrastructure. func generateCSR(_ deviceId: String? = UserProfile.deviceId) -> String? { do { // Define subject DN for CSR let subject = try DistinguishedName([ .init(type: .NameAttributes.countryName, printableString: US), .init(type: .NameAttributes.stateOrProvinceName, printableString: stateProvince_Name), .init(type: .NameAttributes.localityName, printableString: locality_Name), .init(type: .NameAttributes.organizationName, printableString: organization_Name), .init(type: .NameAttributes.organizational

When my app is in the foreground, I receive the notification at 12:13 PM (Indian Standard Time), with the APNs device token: 2bffe3f3800cd7ed7e599495e48051aa1f457ba7de52ea14ddd363bf373d3b08. However, after 6 hours, when I attempt to send a push notification at 6:00 PM (Indian Standard Time), I do not receive the notification, despite using the same APNs device token: 2bffe3f3800cd7ed7e599495e48051aa1f457ba7de52ea14ddd363bf373d3b08.

You’re using a third-party crash reporter and it’s undermining your ability to debug this issue. This is not uncommon. I discuss this in way too much detail in Implementing Your Own Crash Reporter. My advice is that you remove your third-party crash reporter and then wait for new Apple crash reports to arrive. To illustrate the sorts of problems I’m talking about here, let me pull apart that second crash report, starting with this: Exception Type: EXC_CRASH (SIGSEGV) Exception Codes: 0x0000000000000000, 0x0000000000000000 Triggered by Thread: 0 This shows that your process crashed due to a memory access exception. That it, it was running some code that accessed an invalid memory location. Let’s look at the backtrace of the crashing thread: Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib … mach_msg2_trap + 8 (:-1) 1 libsystem_kernel.dylib … mach_msg2_internal + 76 (mach_msg.c:201) 2 libsystem_kernel.dylib … mach_msg_overwrite + 428 (mach_msg.c:0) 3 libsystem_kernel.dylib … mach_msg + 24 (mach_msg.c:3

We have confirmed that the issue has been addressed in both beta 6 and beta 7. Thank you.

@DTS Engineer unfortunately yes. I reproduced with Xcode 26 beta 6 (17A5305f) and an iPad running iOS 26 beta 7 (23A5326a). The following code will produce the runtime exception. slider.addTarget( self, action: #selector(sliderValueDidChange(_:for:)), for: .valueChanged ) // ... @objc func sliderValueDidChange(_ sender: UISlider, for event: UIEvent) { print(event) } whereas changing the event parameter type to UIControl.Event doesn't produce it: @objc func sliderValueDidChange(_ sender: UISlider, for event: UIControl.Event) { print(event) } Do note that changing the action method body to @objc func sliderValueDidChange(_ sender: UISlider, for event: UIEvent) { print(Event: (event)) } has always been working fine, but that is because the String interpolation treats the event value as nil I believe (by printing an empty String).

I can confirm the same issue on iOS 26 beta 6. We have been using simultaneousGesture() as a workaround for the well-known bug, which is the same one BAR115 mentioned earlier. However, this workaround appears to be broken as well. At the moment, it seems there is no reliable way to use buttons inside sheets. This is just ridiculous.