“Popping Sound”

It sounds like you’re trying to use Developer ID signing for day-to-day development. That’s something I recommend you avoid. Rather, use an Apple Development signing identity for development. For background on this, The Care and Feeding of Developer ID. Having said that, I can help you debug this specific problem. I recommend that you start out by isolating this from Xcode. If you run these commands, what do you see: % cp /usr/bin/true MyTrue % codesign -s Developer ID Application -f MyTrue Run these from Terminal, logged into the same GUI login session as you’re using for Xcode. If that prints a no identity found message, what do you see when you run this command: % security find-identity -p codesigning Policy: Code Signing Matching identities … 11) ADC03B244F4C1018384DCAFFC920F26136F6B59B Developer ID Application: Quinn Quinn (SKMME9E2Y8) (CSSMERR_TP_CERT_EXPIRED) 12) 3F8BE319780F84EB2E94ABDFA24E8045A0572A7B Developer ID Application: Quinn Quinn (SKMME9E2Y8) 12 identities found Valid identities onl

I think I follow your point - however, to be clear, I had already dropped the working monitor down to 3008x1692 hiDPI @ 120 Hz (which, from what I looked up online, is 4K @ 120 Hz in terms of pixels being pushed to the screen by the MacBook), How were you making that change? The problem here is that I'm not sure the display settings pane will actually change what we're sending to the screen. Did you see the screen reset when you changed resolutions? Having said that, this does sound like you've forced a real resolution change: So the working state where the MacBook Pro has one monitor connected at 4K @ 240 Hz isn't the true starting point, and I believe even with HiDPI enabled, the refresh rate is changing when I change it in OS settings, because it's a very visible drop particularly down from 100+Hz into 60Hz or 30Hz. Additionally, I've tested the working state where the one working monitor is at, e.g., 1920x1080 low-DPI at 30Hz (very blurry due to low DPI, very visible framerate skips when moving t

This all makes me think that sleep on macOS in the past few years is now defined differently -- perhaps an Apple Silicon change? But I can't find documentation that covers this. Buried in a WWDC video, maybe? I think it was before that. It sounds like you're encountering Dark Wake. It's only hinted at in a couple of places in the documentation. The Power Nap feature is closely related and seems to be more openly acknowledged. But I don't know of any way (for an app) to detect or control when they get triggered. Apple engineers say there's no way to detect it.

Hi Michael, Thank you for the previous suggestion about using AnchorEntity(.head) with trackingMode = .once for positioning entities relative to the user's gaze — that approach worked great for our immersive menu positioning. Now I'm running into a different issue with 360° video playback. When rendering an equirectangular video on a sphere using VideoMaterial and MeshResource.generateSphere(), there is a visible black seam line running vertically on the sphere. This appears to be at the UV seam where the texture coordinates wrap from 1.0 back to 0.0. The same video file plays without any visible seam in other 360° video players on Vision Pro, so the issue is not with the video content itself. Here is the relevant code: private func createVideoSphere(content: RealityViewContent, player: AVPlayer) { let sphere = MeshResource.generateSphere(radius: 1000) let material = VideoMaterial(avPlayer: player) let entity = ModelEntity(mesh: sphere, materials: [material]) entity.scale *= .init(x: -1, y: 1, z: 1) // Flip t

When I tried to create the bug in new project, I found the solution.. First, I added .windowStyle(.hiddenTitleBar) to the WindowGroup in my main app file. It prepares the window to be borderless before the system even draws it. Standard applicationDidFinishLaunching logic was running too early for me. The OS was still setting up its default gray style and overwriting my code. I used a tiny timer to force my settings once the window is actually alive. func applicationDidFinishLaunching(_ notification: Notification) { // I used a 0.1s timer to catch the window AFTER the OS finishes its default setup Timer.scheduledTimer(withTimeInterval: 0.1, repeats: true) { timer in if let window = NSApplication.shared.windows.first { self.setupWindow(window) timer.invalidate() } } } Then re-apply the transparency and separator settings in the windowDidBecomeKey delegate method to stop the focus pop. func windowDidBecomeKey(_ notification: Notification) { guard let window = notification.object as? NSWindow else { ret

@MayankGR thank you for your question! Thank you @JosephSimpson , onWorldRecenter does indeed sound like the event the OP is looking for. This doesn't sound like expected behavior, although more context about your exact use case would help us get to the bottom of this. In case this is a bug, could you please file a bug report using Feedback Assistant? Include as much context as you can, a simple project that reproduces the issue would be perfect. And then could you share the ticket number with us in the thread? Thank you!

Hi zeusqolivar, I'm facing the exact same issue, I was added as admin yesterday and thought it was just a matter of some hours, but for now I still have the same pop-up message.. It is quite annoying as I can't build my app and test it locally because of that.

This issue occurs on iOS 26+, I haven't reproduced this issue yet. According to online monitoring, it occurs in a specific user environment scenario where AVPlayer is used to play background music while the user is playing a mini-game on an H5 page, which also includes in-game audio. I will attempt to reproduce the issue again.