A Summary of the WWDC25 Group Lab

(Continued) Are there best practices for taking an existing swiftUI app and making a two dimentional visionOS app? Compatible iOS apps can run on visionOS, see Making your existing app compatible with visionOS. If you want to go further than compatibility, you can add visionOS as a platform to your Xcode project’s target, and develop with the visionOS Simulator. Principles of spatial design, Design for spatial user interfaces, Design hover interactions for visionOS, and Bringing your existing apps to visionOS will provide you with lots of best practices to apply! I’m aware that baked lighting is often recommended, but is there a supported way to use dynamic lights and shadows on Apple Vision Pro—especially when working natively with RealityKit or Reality Composer Pro? If so, what are the limitations or best practices? RealityKit offers dynamic lights with shadows, limited to 8 dynamic lights at a time in a scene. You can use ShaderGraph to combine baked lighting and RealityKit’s dynamic lights, reference Peti

I have submitted multiple requests to Apple Developer Technical Support (DTS) over the past two months, clearly explaining our use case and referencing the official documentation as well as the above forum thread. I dug into this a bit and found two requests, one from you on 4/27/25 (replied to on 4/29/25) and one from a similarly named company on 6/18/25 (replied to on 6/30/25). Both received the same standard reply we send for that request, which asks a series of questions (A-> E) necessary for us to properly grant the entitlement. Unfortunately, I have either received no response or responses that do not address my request for the special entitlement. What response did you receive? The standard response we replied to both of these requests with opens with this: I’m responding to your request for access to the com.apple.managed.vpn.shared keychain access group. Before we start, I want to clarify one thing. As of Nov 2016, it’s possible for any developer to enable the Network Extension provider e

Thanks @BabyJ. I have updated my code to address the discrepancy which you've noted. My code now looks like this: ` let section = NSCollectionLayoutSection(group: group) let headerSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1.0), heightDimension: .estimated(37.0)) let header = NSCollectionLayoutBoundarySupplementaryItem( layoutSize: headerSize, elementKind: ElementKind.sectionHeader.rawValue, alignment: .topLeading) section.boundarySupplementaryItems = [header] emotionFiltersDataSource.supplementaryViewProvider = { collectionView, kind, indexPath in guard let headerView = collectionView.dequeueReusableSupplementaryView( ofKind: ElementKind.sectionHeader.rawValue, withReuseIdentifier: emotionFiltersHeaderReusableView, for: indexPath ) as? EmotionFiltersHeaderView else { fatalError(Could not dequeue header view as EmotionFiltersHeaderView) } let sectionTitle = Section.allCases[indexPath.section].rawValue headerView.sectionTitleLabel.text = sectionTitle return headerView } Bu

(For posterity and web searches) One can create a serial queue by using the default initializer for DispatchQueue: private let serialQueue = DispatchQueue(label: some.custom.label) I'm then initializing the Connection Group like: connectionGroup = NWConnectionGroup(with: multicastGroup!, using: params) and finally starting it with: connectionGroup.start(queue: serialQueue) It's that last line that's super important because the default global() queue will give you a concurrent queue rather than a serial one.

Ah yes, great point! I think that's exactly what it was. I had fixed the issue initially by processing in a serial queue, but your comment made me go back and realize the connection group was getting started like this: connectionGroup.start(queue: .global()) Which is, of course, a concurrent queue. With the serial queue in place I was able to flood the device with thousands of UDP messages without issue. Thanks so much!

I’m glad to hear you’re making progress. [quote='847078022, FT-cfoy, /thread/791083?answerId=847078022#847078022, /profile/FT-cfoy'] The completion handler is spinning up a new thread [/quote] I noticed that the crashing code is being called out of Network framework. One thing to watch out for there is the type of queue that you pass into Network framework when you create your NWConnection [1]. Network framework will accept either a serial queue or a concurrent queue. Internally it does its own serialisation, so it doesn’t care. However, for your own sanity it’s important to use a serial queue. If you use a concurrent queue, it becomes very hard to reason about your code. Similarly, if you have multiple connections running simultaneously, it often makes sense to use the same serial queue for all of them. Oh, and be wary of concurrent queues in general. See Avoid Dispatch Global Concurrent Queues. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.c

I’m not sure I can properly help you with this, because I’m not confident I understand QA1277, which is problematic because I originally wrote it! Honestly, I’m not sure I fully understood it back then either )-: Regarding your issue, my understanding is that these credentials are generated on successful authentication. However, I’ve never looked into the exact point that generates them, that is, are they generated by the act of successfully gaining a right, or by successfully running a rule, or by the builtin:authenticate method. You can almost certainly work this out by looking at the code for the authorisation engine in Darwin. A good place to start would be here [1]. WARNING You have to be careful when digging into Darwin. It’s full of implementation details, and encoding such implementation details in your product is not the path to long-term binary compatibility. However, in this case I think it’s reasonable. Authorisation plug-in development is already a field full of compatibility pitfalls. If you’re