“A Summary of the WWDC25 Group Lab”

Oh thanks! That might work. I had only tried Xcode 16. I need to be able to work on the project at home and in the college lab. My current home projects won't build in college. There will also be an issue with grading of assignments. I'll try Xcode 16.4. Will that work in college I wonder? They have Xcode 16? I'll try anyway. Thanks so much for you reply!

Hi Quinn, I followed your steps and the profile dump is as below. It has com.apple.developer.payment-pass-provisioning => 1 : { AppIDName => XC com s_ _ _ _ _ _ d ApplicationIdentifierPrefix => [ 0 => 2 _ _ _ _ _ _ 7 ] CreationDate => 2026-02-05 15:09:44 +0000 DER-Encoded-Profile => {length = 3857, bytes = 0x30820f0d 06092a86 4886f70d 010702a0 ... 73b0c49b eb3ffec9 } DeveloperCertificates => [ 0 => {length = 1487, bytes = 0x308205cb 308204b3 a0030201 02021007 ... b474d99f 14730350 } ] Entitlements => { application-identifier => 2 _ _ _ _ _ _ 7.com.s _ _ _ _ _ _ d aps-environment => production beta-reports-active => 1 com.apple.developer.associated-domains => com.apple.developer.in-app-payments => [ 0 => merchant.com.s_ _ _ _ _ _ d ] com.apple.developer.networking.slicing.appcategory => [ 0 => communication-9000 1 => games-6014 2 => streaming-9001 ] com.apple.developer.networking.slicing.trafficcategory => [ 0 => defaultslice-1 1 => video-2 2 =

Hello @Developer Tools Engineer , Thank you for supporting. I've tried to delete previews sims but the issue was not solved. I'm using the Company Managed Device so I don't have permission to logging profile. I can share you summary text of Preview, Could you take a look on that? Thank you, Cuong Trinh previews_diagnostics_summary.txt

[quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profile/TotalPhase'] We haven't setup a VM yet. [/quote] I strongly recommend that you do. It has some key benefits: It strictly constrains the problem space. For example, if you have a bug with identifying the correct broadcast interface [1], such a problem will go away in a VM because there’s only one interface. So, if the local network alert always shows up in a VM but fails on real hardware, it’s likely that this isn’t an issue with local network privacy per se, but something in your code. It makes it much easier to run tests in isolation. You can quickly iterate on your tests, creating a new clone of your ‘clean’ VM each time. It allows you to test across OS releases. If you think something broke in, say, macOS 26.2, you can easily test 26.1, 26.2, and 26.3 beta, all in parallel. Debugging these problems on real hardware just makes things harder. [quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profil

Hi Michael, Thank you for your previous suggestion to use ViewAttachmentComponent for immersive controls. I've implemented it, However, I'm still facing two critical issues: Issue 1: Buttons in ViewAttachmentComponent Not Responding to Gaze + Pinch The buttons inside my ViewAttachmentComponent are visible and render correctly, but they do not respond to eye gaze + pinch gestures. This defeats the purpose of using visionOS's hands-free interaction model. My Implementation: ImmersiveView.swift (for panoramic images): struct ImmersiveView: View { @EnvironmentObject var model: AppModel @State private var menuEntity: Entity? @State private var isMenuVisible: Bool = true var body: some View { RealityView { content in // Invisible sphere for gesture detection let tapDetector = Entity() tapDetector.name = TapDetector tapDetector.components.set(CollisionComponent(shapes: [.generateSphere(radius: 900)])) tapDetector.components.set(InputTargetComponent()) content.add(tapDetector) // Create control menu using ViewAttachm

Thanks for all the details and the funny anecdote. I'll ask the user to run the cp command, but they told me they have some other work to do at the moment and need a break. In the meantime, since you said it's a SMB issue, is there a way I can reproduce the Result too large myself? Yes. To start with here: Setting a large resource fork like mentioned in that StackOverflow post causes the mentioned error Argument list too long. Was this on your SMB target or on your local (APFS) volume? If this is happening on the local volume, then I think the problem is that you're hitting the max transfer size limitation of fsetxattr. You need to break the transfer up into smaller individual segments, as copyfile does here. As a side note here, there's an open question here as to how the problem file originally got to the SMB server. On modern systems, we primarily use the resource fork to store compressed data (as I described above), but we also got out of our way to NOT export that configuration out of the system. You can