DTiPhoneSimulatorErrorDomain Code 2

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Regarding this: it doesn't seem to be an issue with DenyMulticast I don’t think multicast is a factor here, either for good or for ill. iOS has additional restrictions around multicast, but those do not apply on macOS. this command always works for any user When run how? From Terminal? If so, that’s not the evidence that you think it is. Quoting TN3179: macOS automatically allows local network access by: Any daemon started by launchd Any program running as root Command-line tools run from Terminal or over SSH, including any child processes they spawn Based on the info you’ve provided so far, it really does sound you’re bumping into local network privacy issues. This is complicated by the fact that Unix-y programs tend to do things that confuse local network privacy, for example: Common Unix-y techniques, like calling daemon man page, can break responsible code inference. Such p

I am developing a macOS virtual audio device using an Audio Server Plug-In (HAL). I want the virtual device to be visible to all applications only when my main app is running, and completely hidden from all apps when the app is closed. The goal is to dynamically control device visibility based on app state without reinstalling the driver. What is the recommended way for the app to notify the HAL plug-in about its running or closed state? Any guidance on best-practice architecture for this scenario would be appreciated. So, full disclaimer, I don't have a lot of direct experience with AudioServer plugins, so the advice I'm giving is coming from a general device management/architecture perspective, NOT from detailed experience with this particular plugin type. In any case, the place I would probably start with here is the sample project Building an Audio Server Plug-in and Driver Extension. You don't need any kind of DEXT for this, but that sample does how to deal with device appearance/disappearance, which is

Hello! I’m not a Distinguished Winner, but I did win last year. In my experience, it takes time. For examples of strong projects, see https://wwdcscholars.com/ (not endorsed by Apple). It showcases many past winners and helps you understand what judges look for. Don’t expect to win on your first try. It’s competitive, and I needed two failed attempts before a winning submission. I focus on the intersection of my interests, problems I’ve identified, and native Apple technologies. That keeps me motivated by the problem I’m solving. Remember that the app is only part of the challenge. Don’t underestimate the essay. Make sure your app and essay reflect who you are as a developer. In my experience, judges care more about your motivations and the problem you’re tackling than a perfectly polished solution. The idea is the most important part, and it often takes the longest. This year, I went through three different ideas before landing on one I’m happy with. Hope this helps, and good luck!

So, looking at things from our side, I'm not sure. I found one bug on this (r.166518515) about accessing a custom directory (/Library//), but the analysis of the engineering team is that it isn't a bug in macOS 26.2... because it shouldn't work in macOS 26.0 EITHER. More specifically, it should only be accessing one of these documented directories: 2. Writing of files: pursuant to normal UNIX file permissions, filters and backends can read/write files to the cache directory specified by the CUPS_CACHEDIR environment variable, to the state directory specified by the CUPS_STATEDIR environment variable, to the temporary directory specified by the TMPDIR environment variable, and under the /private/var/db, /private/var/folders, /private/var/lib, /private/var/mysql, /private/var/run, /private/var/spool (except /private/var/spool/cups), /Library/Application Support, /Library/Caches, /Library/Logs, /Library/Preferences, /Library/WebServer, and /Users/Shared directories. FYI, that does suggest a possible wo

@DTS Engineer thanks for the info! On #2, calling open(_:options:completionHandler:) when Allow Full Access is not turned on results in an error (only as of iOS 26, it worked in iOS 18): unable to make sandbox extension: 2 Failed to open URL : Error Domain=NSOSStatusErrorDomain Code=-54 (null) UserInfo={_LSFile=LSOpenOperation.mm, _LSLine=835, _LSFunction=_LSIsRequestAllowed} Is there a solution to open the app without forcing the user to turn on full access before they can use the keyboard?