A Summary of the WWDC25 Group Lab

Interesting. That setup shouldn’t trigger a TCC alert. Do you see the problem if your run the app on a fresh system? That is, one that’s never seen your app before? App group containers do record the identity if the code that created them, and that can sometimes confuse things, so it’s best to verify the result on a fresh Mac. I generally use a VM for this, restoring it to a fresh snapshot between tests. However, you can also do this by creating a new user account on your main Mac. And once you get into the swing of things, you can simple delete the container from ~/Library/Group Containers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I'd really appreciate any concrete tip on how I should save the document, because everything I've tried doesn't work. Simply calling updateChangeCount(_:), like we already saw, messes with the undo mechanism. How is the text view able to save everything I input when the window first appears and then quit the app, but isn't able to when switching to another app and back again? This is the last thing I tried, and when quitting the app the .terminateNow branch is always executed. Just calling endUndoGrouping() without beginUndoGrouping() logs an error in the Xcode console that no undo group is currently open. func applicationShouldTerminate(_ sender: NSApplication) -> NSApplication.TerminateReply { for document in documents { document.undoManager?.beginUndoGrouping() document.undoManager?.endUndoGrouping() } let edited = documents.filter({ $0.hasUnautosavedChanges }) if edited.isEmpty { return .terminateNow } var remaining = edited.count for document in edited { document.autosave(withImplicitCancella

It was a third-party application developped by Nik Software. It was the lastest release on macOS in 2012. Many years after, Google bought editor, improve software and now you can only use it on IOS or Android platform. Thanks for your answer, I'll look about Nik Software and how to contact developers, there is a group of names in topic 'About Snapseed'.

On my Mac mini M4 Pro, I’ve installed macOS Tahoe 26.0 and Xcode 26.0.1. The error message still appears, even when testing with the iPhone 17 Pro and iPad Pro 11-inch M4 simulators. The FB numer is: FB20362054 == PREVIEW UPDATE ERROR: GroupRecordingError Error encountered during update group #19 ================================== | FailedToLaunchAppError: Failed to launch net.thomasbayer.ChatPrototype | | ================================== | | | [Remote] JITError | | | | ================================== | | | | | [Remote] CouldNotLoadInputObjectFile: Could not load object file during preview: /Users/thomas/Library/Developer/Xcode/DerivedData/ChatPrototype-ebbbmisjgapzykawaadxudtxyjmg/Build/Intermediates.noindex/ChatPrototype.build/Debug-iphonesimulator/ChatPrototype.build/Objects-normal/arm64/ChatPrototypeApp.o | | | | | | path: /Users/thomas/Library/Developer/Xcode/DerivedData/ChatPrototype-ebbbmisjgapzykawaadxudtxyjmg/Build/Intermediates.noindex/ChatPrototype.build/Debug-iphonesimulator/ChatProt

CloudKit Push Notifications Not Delivering - Extensive Debugging Completed Issue Summary CloudKit subscriptions are properly configured and triggering, but push notifications are never delivered to devices. After extensive debugging, I've isolated the issue to CloudKit→APNS delivery failure. Environment Xcode: 15.x iOS Target: 17.0+ watchOS Target: 10.0+ CloudKit Database: Both Public and Private Testing Devices: iPhone 15 Pro, Apple Watch Series 9 Environments Tested: Development and Production What's Working ✅ 1. CloudKit Subscriptions All 6 subscription types successfully created and visible in CloudKit Dashboard Subscriptions persist across app launches (verified in dashboard) Subscription predicates correctly configured for each record type: // Example: FriendRequest subscription NSPredicate(format: toUser == %@, userRecordID) // Example: Challenge subscription NSPredicate(format: recipientID == %@ AND status == %@, userRecordID, pending) 2. Device Registration • App successfully requests and re

Hello, I’m experiencing a very unusual problem when using VirtioFS with the Apple Virtualization Framework and Docker, through tools such as Lima and Tart. I’ve described the full details here: lima-vm/lima#4053 (comment), but here’s a quick summary. Steps to Reproduce Given a directory structure like this: mkdir -p local-test-dir/dir and running the following command: docker run -u $(id -u) --rm -v $PWD/dir:/mnt/dir alpine:latest sh -c ls -al /mnt the output is: total 8 drwxr-xr-x 1 root root 4096 Sep 23 22:48 . drwxr-xr-x 1 root root 4096 Sep 23 22:48 .. drwxr-xr-x 2 root root 64 Sep 19 21:34 dir # <-- INCORRECT The directory appears as root:root, which is wrong. Workaround If I add an artificial sleep of more than 0.9s before listing the directory, the issue disappears: docker run -u 501 --rm -v $PWD/dir:/mnt/dir alpine:latest sh -c sleep 0.9; ls -al /mnt Output: total 8 drwxr-xr-x 1 root root 4096 Sep 23 22:48 . drwxr-xr-x 1 root root 4096 Sep 23 22:48 .. drwxr-xr-x 2 501 root 64 Sep 19 21:34