A Summary of the WWDC25 Group Lab

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

Hello @Plight , thank you for your question! First, could you please share more about what you are trying to do in your app? Its difficult to give advice on workflows without knowing exactly what kind of experience you are trying to create. Most of our existing documentation is going to be from WWDC videos, like the one you linked above, and the documentation website for specific APIs. Here's another WWDC25 video where we go over the Apple Positional Audio Codec (APAC) near the end: Learn about the Apple Projected Media Profile. It provides an example of how to author an audio file using AVAssetWriter. Davinci Resolve is currently capable of authoring ambisonic ASAF content, so I recommend investigating that tool to see if it meets your needs. Additionally, Resolve should be cabable of encoding an ASAF master wav file into APAC. The Compressor app also has this functionality. You can use the AVPlayer API to playback ASAF content in your app. This is available on a VideoMaterial for example. Please se

Hello @Plight, thank you for your question! First, could you please share more about what you are trying to do in your app? Its difficult to give advice on workflows without knowing exactly what kind of experience you are trying to create. Most of our existing documentation is going to be from WWDC videos, like the one you linked above, and the documentation website for specific APIs. Here's another WWDC25 video where we go over the Apple Positional Audio Codec (APAC) near the end: Learn about the Apple Projected Media Profile. It provides an example of how to author an audio file using AVAssetWriter. Davinci Resolve is currently capable of authoring ambisonic ASAF content, so I recommend investigating that tool to see if it meets your needs. Additionally, Resolve should be cabable of encoding an ASAF master wav file into APAC. The Compressor app also has this functionality. You can use the AVPlayer API to playback ASAF content in your app. This is available on a VideoMaterial for example. Please sen

Please review the following resouces, they should be helpful in learning about SwiftUI layouts: Building layouts with stack views Picking container views for your content Grouping data with lazy stack views Composing custom layouts with SwiftUI

In your case, the changes in your text view don't go to the undo stack Only the last changes, all previous other changes do as expected. save the document as needed That is what I'm wondering about. What is the correct way of nudging the undo mechanism so that autosaving would see the document as dirty? We already saw that simply calling updateChangeCount(_:) breaks the undo mechanism. though AppKit folks may see the current behavior, which skips the save for a clean document when terminating the app, as correct Skipping save for a clean document is correct in my opinion as well, but the problem is that the document should not be clean in this case, and the question is how it should correctly be marked as dirty without breaking the undo mechanism. The text view probably has an open undo group (waiting for more text to be inserted) that should be closed when trying to quit the app, so that the document is then correctly marked as dirty.

The app group that was formerly used to store data while the app was distributed with the other developer's account will have the other developer's App ID Prefix and will not be accessible from your account. App groups you create in your account will have your account's App ID prefix and data stored using them will be private to your account.