DTiPhoneSimulatorErrorDomain Code 2

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?

Thank you for your post. I find your question quite intriguing, as SwiftUI observable variables are undoubtedly a powerful feature we all use. However, I am not the best developer to provide you examples as I don't use many third parties anymore based on my job. I can provide an example of how I handle third-party libraries that conform to ObservableObject, or at least I did. There is no definitive answer from me, but developers must always adapt to the challenges they encounter. // ObservableObject wrapper for MyObservableType class ObservableTypeAdapter: ObservableObject { @Published private var myObservable: MyObservableType When dealing with imported code that employs a different observation technique than the one you are utilizing in your SwiftUI project, you can bridge the gap between the two by employing certain adaptation techniques. If you have an existing type and require it to be used in a context that expects the macro format, you can create a wrapper that conforms to the expecte

@DTS Engineer Thank you for the reply, I have tried resetting my router, restarting my Mac, and also tried different networks. But it's the same issue. I don't have firewall or Anti virus installed and still same error. Xcode is fully updated (latest) MacOS is Tahoe 26.1 (latest) As you can see, using cli still throws similar error ➜ ~ xcodebuild -downloadPlatform iOS Finding content... Automatically resolved architecture variant for platform iOS as 'arm64'. 2026-01-07 22:09:14.742 xcodebuild[71859:6206960] DVTDownloadable: Download Failed. Downloadable: { architectures = ( arm64 ); authentication = none; category = simulator; contentType = cryptexDiskImage; dictionaryVersion = 2; downloadMethod = mobileAsset; fileSize = 8388683973; identifier = com.apple.dmg.iPhoneSimulatorSDK26_2_arm64; isInternalContent = 0; isUserInitiated = 1; name = iOS 26.2 Simulator (23C54); patchableFrom = ( ); platform = com.apple.platform.iphoneos; simulatorVersion = { buildUpdate = 23C54; version = 26.2; }; version = 26.2

Hey @dev52, I'd recommend that you get started with various pathways that you find reverent to your journey. In particular you might want to look at the Design, visionOS, and Enterprise pathways. These pathways are easy-to-navigate collections of videos, documentation, and tools. Additionally you might want to watch some prior WWDC session videos available here. There is a lot of documentation, sample code, and videos to uncover. Let me know if you have any questions. If you have a specific issue that you need assistance with, please open up a new thread. Thanks, Michael

Hello extraman, Thank you for reporting this issue. Can you please provide the code for the view that the .toolbar modifier is attached to, that reproduces this issue? Or do you have a small test project demonstrating it? If so, please share a link to your test project. This will help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Thank you for your patience, Richard Yeh  Developer Technical Support

You'd need to generate a set of Path instances from the characters in your text. This is only really suitable for small amounts, e.g. the Welcome animation or clock digits, etc., because it's not the most performant thing. Also, bigger text is better. Lastly, remember to wrap it all in a GlassEffectContainer to avoid each character's glass being rendered in a discrete pass. Actually lastly: you'll need to adjust the location of the text using .offset(x:y:) or by tweaking the path creation to include better offset translations. This is my quick & dirty attempt. Since .glassEffect() is designed similarly to a fill API, you need something non-empty to 'fill' with your text. Color.clear gets elided by the rendering engine, but what I've found is that Color.white.opacity(0) works to cause an actual (invisible) view to render and take up space during layout calculations. And now: the code! This was written for tvOS, so it uses BIG fonts and offsets to write big numbers. I had it draw a counter that inc

Hey @UXUiOS, This seems like a bug, but I'd like the relevant teams to take a look. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report, include a video of the issue and sample code that replicates the problem, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report. Thanks, Michael

We are seeing this behaviour even with mounted disk images. We will test with AFP server also. We are not seeing this behaviour when we copy using cp or mv terminal commands or any other application. It’s certainly due to some changes in DesktopServicesHelper on macOS Tahoe which triggers file deletion if it takes more than 5 seconds to transfer. We have tried with less than 5 seconds like 4.5 sec or 4.9 seconds and it works as expected. Interesting. I spent some time looking at our code today and, while I wasn't able to find the specific change, there were a number of operation timeouts added to the copy architecture as part of resolving a number of hangs and other issues. None of them exactly match what you're describing, but the Finder's copy implementation is sufficiently complex that it's likely that I simply missed something. A few different comments: I should have asked this earlier, but what's the auth event you’re actually blocking and are you sure it's something you SHOULD be blocking? Nota