Popping Sound

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. P

There's .pkpasses format, which is a zip file (just like .pkpass) with several .pkpass inside, but apparently this is supported only in Safari and Mail (still don't understand why but this sounds stupid)

Maybe I'm a little late to join the party, but it sounds like the endpoint you are listening to might wrong. The endpoint is: /v1/passes/{passTypeIdentifier}/{serialNumber} And the endpoint is appended after your webServiceURL. Another thing, that endpoint is called only when the list endpoint returns some changes. For each change returned from the response of the list endpoint, Wallet will perform an HTTP request to your update endpoint to ask for a new pass.

Please check the crash files as attached. So, this is a great example of why I always ask for a crash log, as the problem here doesn't actually have anything to do with the audio system itself. The problem is that your app is stuck in an infinite loop. For future reference, the most direct proof of this is that the number of stack frames on the crashing thread is very high (860) and that the base of the stack ISN'T a valid entry point for a thread. For the main thread, this would be main, but other threads would be thread_start or a similar entry point in libpthread. Crash collection system artificially limits the number of frames it collects (otherwise you'd potentially have 1000s+ of lines of repeating frames), so you aren't actually getting the true bottom of the stack. 858 <...> closure #1 in DeviceManager.init() + 80 859 <...> partial apply for closure #1 in DeviceManager.init() + 24 (/:0) 860 <...> closure #1 in NSNotificationCenter.addObserver(forType:object:queue:using:) + 2

You’re relying on framework versions? Actually, no — that’s just how Chromium organizes its build. Is the local network call being made by the process running your app’s main executable? Or by, perhaps, a helper tool embedded in this framework? Chromium does network request out of Main process, in helper process in framework. /Applications/Comet Dev.app/Contents/Frameworks/Comet Dev Framework.framework/Versions/140.0.7339.20748/Helpers/Comet Dev Helper.app/Contents/MacOS/Comet Dev Helper --type=utility Here I prepared two videos with demos: Usually it is easy reproducible when open Google meet… Here I run a regular build with local network permissions, mount the new build, run rsync, and catch the issue: https://www.loom.com/share/0e1dcafdf6c645e9a34087e36414bc78 As an experiment, I also prepared two builds with a static UUID for each Mach-0 generated by my patched LLD (UUID based on hash of the filename): https://www.loom.com/share/d48b6365a4154a3ba8da8f921ad445ca In this case I cannot reproduce the issue —

Looking around, sounds like perhaps the 4096 also needs to hold tokens beyond the content? If correct, it would be nice to have this broken out better in the error or something similar because just reading this makes it sound like a framework bug.

[quote='801397021, chapo213, /thread/801397, /profile/chapo213'] I have a VPN product for macOS. [/quote] It sounds like your VPN product isn’t based on the Network Extension (NE) provider architecture. Is that right? If so, there’s not much I can do to help you out here. On macOS the routing table is ‘owned’ by system infrastructure. You can’t safely modify it behind the system’s back. If you do, you’ll run into all sorts of weird problems. This has been true since the dawn of Mac OS X but, historically, you had to bend the rules to create a VPN product. That’s not been the case since we introduced support for NE providers back in macOS 10.11. At that point DTS stopped supported such shenanigans; we now only support VPN products based on the NE provider architecture. This year at WWDC the NE team went out of their way to clarify their position on this. See WWDC 2025 Session 234 Filter and tunnel network traffic with NetworkExtension, starting at 7:26. Oh, and if you are using an NE provider and NE i

It sounds like your VPN configuration is claiming the default route [1]. When it does that, the system uses its VPN’s DNS resolver by default. See this post. [quote='801410021, Shilishper, /thread/801410, /profile/Shilishper'] Is anything can be done about this, programmatically? [/quote] No. Well, not directly. When using the built-in VPN transports, like L2TP, there are three ways to configure the VPN: Manually in System Settings Via a configuration profile Programmatically, using the Personal VPN feature The first two don’t support folks programmatically tweaking the configuration. The last one gives you some control over VPN configuration, but it doesn’t let you change the default route. That’s determined based on the configuration coming back from the VPN server. ps For VPN configuration issues, you might have more luck asking over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. DevForums is primarily focused on APIs, and that’s a