“Popping Sound”

This sounds very similar to the issue discussed in https://developer.apple.com/forums/thread/700648. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

We're also getting the same error ... encountered an error (The test runner hung before establishing connection.) We tried nearly everything, including disabling the Thread Performance Checker in the test scheme shutting down all emulators via xcrun simctl shutdown all and erasing them xcrun simctl erase all force killing any potential hanging simulators beforehand clearing all Simulator logs and caches restarting the machine(s) But this still keeps popping up intermittently. We're using Xcode 26.2. Any tips on what we might want to try next? Thanks!

AudioOutputUnitStart takes ~500 ms I messaged the engineer who owns the PTT framework about this, but my initial reaction is that this is about what I'd expect. Activating the PTT session is inherently slower than direct activation, as it requires both significantly more IPC than standard activation (as the request goes through callservicesd and then the audio system) and the system needs to play the recording alert tone before turning control to your app. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

At this point, all of the items deleted in step 2 have been re-downloaded onto Device B. This doesn't sound right. I'd expect the following behavior: a. If the deletion on device A (step 2) has already synchronized, the records would have been deleted from the server, and so would not be available for device B to download. b. Otherwise, the records deleted on device A still exist on the server, and so would indeed be downloaded to device B, and yet, once the changes on device A is synchronized, device B should get the deleted record IDs when it fetches changes with a valid server change token (and hence remove records from the local cache). So the data will eventually synchronized. c. If the changes on device A is synchronized concurrently while device B is fetching with nil token, device B should get the deleted record IDs as well (and hence remove the records), as mentioned in the second bullet in my previous post. If you observe a different behavior, please share the details and I'd take a closer

Hey @Travel_Immersive, No, .windowStyle(.plain) should not affect button interaction behavior. In terms of creating a window that completely hides itself, I might suggest that you try a different approach. While you can have a window with no content and set the preferred visibility of the system controls to hidden, this is not the best approach as it still could leave the user with floating system UI that isn't attached to anything. Additionally, as this is a window that has system UI, the user could close this window at any time and you'd want to account for this. It sounds like your experience might be better suited to using an ViewAttachmentComponent. Have you considered placing your immersiveControlMenu as the root view of a ViewAttachmentComponent in your immersive view? This way you can animate the visibility of this view and you fully control when and where this view is presented. Let me know if you what you think, Michael

[quote='874373022, TotalPhase, /thread/814226?answerId=874373022#874373022, /profile/TotalPhase'] Our engineers have thoroughly followed the practices outlined in TN3179. [/quote] Cool. I’m pretty sure there are mysterious extant problems with local network privacy, especially on the Mac. However, the ones I’m aware of are much harder to reproduce [1]. In your case it sounds like you can reproduce this 100% of the time. For example: You set up a VM that’s never seen your app before. You install the app on that VM. You start it up. It’s blocked from performing local network operations. And it never displays the local network alert. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For example, the one in this thread

While this isn't the answer I had been wishing for it does give me a lot of food for thought. Thanks The Eskimo for looking into it! [quote='874248022, DTS Engineer, /thread/814022?answerId=874248022#874248022'] When it rotates a file, the system calculates how fast it filled up. [/quote] So wrt this note, I understand it's more complicated than just rotating a single file, but still it sounds like everyone writing into the Unified Logging system can contribute to this. It strikes me at least one strategy (if not a preferable one), is to disable logging for all other processes/subsystems (even some of the native OS processes) that tend to be noisy too? Of course this is meant as a temporary and desperate measure, in theory it should raise our survival chance? And another thought, what if we disable persisting, but then have an external party help redirect our logs to be persisted? I first thought the xctrace record --template Logging might be a good candidate for this task but later found out the def

Hello Kevin, hello All I have tested your suggestions. Sadly to no avail. The location of the files is not crucial nor using a signed version of the app. I have also setup a new project on my macOS14 Mac with the same result. So it is not a macOS26 problem neither. That makes me wonder more and more. My AppStore app (bcAnalyze) that does use the related file feature with these files works well on any macOS with these files. The code I am using is older dating back ca. 10 years (originated in Obj-C days and is now Swift since ca. 4 years). The idea of adding a security scoped bookmark to the sidecar file is tempting, but wouldn't help since the original application producing the the sidecar file is more than 10 years old and users may have already millions of file pairs. There shouldn't be a difference between SwiftUi and AppKit as front-end, but I may also try this in the next days. Since my AppStore app works, I must oversee something little that has this big effect. I can't otherwise explain the negative re

Hi Ziqiao, thanks for the reply. Let me explain the situation I'm facing with my CloudKit-powered app. Device A and B are both fully synced with the cloud. On Device A, the user deletes a bunch of records and continues to use the app, letting the app sync in the background. The user waits a few weeks before opening the app on Device B. When they open the app, it attempts to sync. The change token is expired, so it retrieves all of the records on the server. My app is designed to treat this as if this is the user's first sync (a unify sync), so it compares all records on the server with all local records, then uploads any local records missing from the cloud and downloads any cloud records missing from the local database. At this point, all of the items deleted in step 2 have been re-downloaded onto Device B. Currently, my app never checks deletedRecordIDs on a unify sync. An easy fix would be to start processing this array even on unify syncs. But from your reply, it sounds like this will be an empty

Right now I've got the same error and don't know how to handle it. But in my case I'm recording audio on the Apple Watch with AVAudioEngine. I minimized the app during recording and started 1sec timer. When timer fires, I'm getting interruption began event where I pause recording, when I stop timer's alarm, I have interruption end event with shouldResume and I'm trying to do AVAudioEngine.start(). That's where I have this error.

Sorry for the confusion, and you assumed correctly that copying in the Finder works, but I actually meant something else. What I meant was this: a user of my app reported that when my app copies files from a QNAP NAS to a folder on their Mac, they get the error Result too large. When the app copies the same files from the Desktop folder, it works. Copying the files with the Finder, regardless of their source location, works as well. Yes, that all makes sense. There are basically two different issues that work here: There appears to be a bug in SMB involving the handling of larger xattr. The issue is specific to smb, which is why this doesn't affect local file copies. The Finder uses its own copy engine, which bypasses the problem. More specifically, the Finder is almost certainly using the ..namedfork/rsrc accessor that StackOverflow post mentions. Covering a few details: Interestingly, the destination file is actually created but has a much smaller size than the source: 250 KB instead of 34 MB. The initial f

Right. This is werder than I thought. It IS connecting to the USB microphone, but is applying a brickwall filter to the audio, cutting off everything above 30kHz. I need to talk to somebody at Apple about this behaviour.