A Summary of the WWDC25 Group Lab

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.

The issue is reproduced with a provisioning profile embedded that has the com.apple.security.application-groups set { AppIDName => Cyberduck ApplicationIdentifierPrefix => [ 0 => G69SCX94XU ] CreationDate => 2025-09-23 07:54:54 +0000 DER-Encoded-Profile => {length = 3604, bytes = 0x30820e10 06092a86 4886f70d 010702a0 ... 7013d550 78b027d9 } DeveloperCertificates => [ 0 => {length = 1448, bytes = 0x308205a4 3082048c a0030201 02020854 ... bd543e5c c872b843 } ] Entitlements => { com.apple.application-identifier => G69SCX94XU.ch.sudo.cyberduck com.apple.developer.icloud-container-identifiers => [ ] com.apple.developer.icloud-services => * com.apple.developer.team-identifier => G69SCX94XU com.apple.developer.ubiquity-container-identifiers => [ ] com.apple.developer.ubiquity-kvstore-identifier => G69SCX94XU.* com.apple.security.application-groups => [ 0 => G69SCX94XU.* ] keychain-access-groups => [ 0 => G69SCX94XU.* ] } ExpirationDate

The issue is reproduced with a provisioning profile embedded. The output of security cms -D -i is { AppIDName => Cyberduck ApplicationIdentifierPrefix => [ 0 => G69SCX94XU ] CreationDate => 2025-02-03 20:45:33 +0000 DER-Encoded-Profile => {length = 3546, bytes = 0x30820dd6 06092a86 4886f70d 010702a0 ... 8f791dc8 806888ea } DeveloperCertificates => [ 0 => {length = 1448, bytes = 0x308205a4 3082048c a0030201 02020854 ... bd543e5c c872b843 } ] Entitlements => { com.apple.application-identifier => G69SCX94XU.ch.sudo.cyberduck com.apple.developer.icloud-container-identifiers => [ ] com.apple.developer.icloud-services => * com.apple.developer.team-identifier => G69SCX94XU com.apple.developer.ubiquity-container-identifiers => [ ] com.apple.developer.ubiquity-kvstore-identifier => G69SCX94XU.* keychain-access-groups => [ 0 => G69SCX94XU.* ] } ExpirationDate => 2043-01-30 20:45:33 +0000 IsXcodeManaged => 0 Name => Cyberduck Distribution Provisioning Pro

Thanks. Your code doesn't do step 2, and that's why your changes are lost. But again, even without doing that, the document is regularly saved, so the fact that the very last changes are not saved is, from my point of view, unexpected behaviour. I came across NSDocument.updateChangeCount(_:) some time ago, but concluded that I shouldn't interfere with automatic saving done by the text view. For instance, when using your latest code, if I type anything in an empty document, then undo all the changes and try to close the now empty document, it presents a save panel. This doesn't happen when I just let the text view track the changes (which is also what I would expect). The documentation for that method reads: If you are implementing undo and redo in an app, you should increment the change count every time you create an undo group and decrement the change count when an undo or redo operation is performed. Note that if you are using the NSDocument default undo/redo features, setting the document’s edited

Looks like Kevin and I are gonna be tagging teaming this one (-: [quote='859320022, reidly, /thread/800689?answerId=859320022#859320022, /profile/reidly'] do you mean making sure the logging doesn’t somehow cause a “rearrangement” of the internal details of the code? [/quote] Kinda. When dealing with problems like this, any change to the code could perturb things so that the problem goes away, comes back, or whatever. For example, if the issue is timing related, the act of adding a single log point can change the timing to mask the issue. So there’s a balance to be struck here. You want to add logging, but not at the expense of reproducibility. [quote='859320022, reidly, /thread/800689?answerId=859320022#859320022, /profile/reidly'] I am still trying to understand how a particular arrangement of our code can cause NULL to be “run”. [/quote] When you write code in a high-level language, that code is defined to execute in terms of a virtual machine. For example, the C virtual machine for this code code: int a;

What does this report: % security cms -D -i Cyberduck Nightly.app/Contents/embedded.provisionprofile | plutil -p - I would expect to see the profile authorise your claim to com.apple.security.application-groups > G69SCX94XU.duck. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sorry I didn’t respond sooner. Forums had a bug where it was dropping notifications, and it looks like that’s what happened here )-: Fortunately we’ve just rolled out a fix for that bug (-: [quote='847936022, Deej620, /thread/725152?answerId=847936022#847936022, /profile/Deej620'] When attempting to call SecItemCopyMatching, I'm getting a -34018 missing entitlement error. [/quote] The answer here varies based on whether you’re targeting macOS or iOS. Let me summarise, starting with iOS: Every provisioning profile authorises access to com.apple.token. But you must claim that access by listing com.apple.token in your keychain-access-groups list. WARNING Adding items to keychain-access-groups can change your default keychain access group, and doing that unexpectedly is a common source of confusion. Read Sharing access to keychain items among a collection of apps for more on this. For macOS: It’s not possible to create a provisioning profile that authorises access to com.apple.token. Bu