eskimo

I’ve been talking to my Frameworks Engineer colleague about this and there are various reasons why this might be happening. To investigate further, I have a couple of tests I’d like you to run. The first is to run launchctl procinfo against your process % sudo launchctl procinfo `pgrep Test807154` … code signing info = get-task-allow entitlement require enforcement allowed mach-o platform dyld entitlements validated … IMPORTANT Replace Test807154 with the name of your app. Do you see the entitlements validated flag set? Second, dumy your Launch Services database: % lsregister -dump Note lsregister is actually /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister. I have a shell alias that maps the former to the latter. Then find the record for your app. In my case it looked like this: -------------------------------------------------------------------------------- bundle id: Test807154 (0x1a02c) class: kLSBundleClassApplication (0x2) … path: …/Test

Thanks for those bug reports. Using them I was able to track down the lead bug for this (r. 162628085). AFAICT this isn’t fixed in any shipping or seeded version of Xcode, up to and including the current Xcode 26.2b2 (17C5038g). However, as always, I encourage you to re-test with new seeds as they’re released. In the meantime, it’s possible that you might be able to work around this crash by pass absolute paths, rather than relative paths, to xcresulttool. Please try this and lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, I have limited experience with this myself (gotta get my boss to buy me a shiny new iPhone 17 :-) but I think the best place to start is a crash report. If you detach the debugger from the process, the system should generate one. For more details on how to do this, and how to post the report here, see Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I tried this here in my office and didn’t see any leaks or unbounded memory growth. Here’s what I did: Using Xcode 26.1 on macOS 15.7.1 [1], I created a new project from the macOS > Command Line Tool template. I then added a dynamic library target to that. I populated them with the code shown at the end of this post. I build both targets using Xcode. I then ran the tool from Terminal: % ./Test806035 will run will open and close, iteration: 0 did close and close … will open and close, iteration: 999 did close and close did run, press return to loop, pid: 47371 In other Terminal window, I rans leaks against the process. It showed no leaks. I ran heap against the process: % heap Test806035 … COUNT BYTES AVG CLASS_NAME TYPE BINARY ===== ===== === ========== ==== ====== 134 4288 32.0 Class.data (class_rw_t) C libobjc.A.dylib 27 11360 420.7 non-object 5 512 102.4 xpc_string_t (Storage) C libxpc.dylib 5 256 51.2 xpc_dictionary_t (Storage) C libxpc.dylib 5 240 48.0 xpc_string_t ObjC libxpc.dylib 4 128 32.0 Class.m

Hmmm, that’s the human readable file. Do you have the JSON version of it? The file you attached here shows the format I’m looking for. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='866732022, arnair, /thread/798893?answerId=866732022#866732022, /profile/arnair'] to know whenever the user switches the wifi network on device from iOS 26 onwards [/quote] That’s not a supported use case for the Hotspot Helper subsystem. Quoting TN3111 iOS Wi-Fi API overview: NEHotspotHelper is only useful for hotspot integration. There are both technical and business restrictions that prevent it from being used for other tasks, such as … The same comment applies to the new hotspot providers, except moreso. They are ever more tightly restricted than hotspot helper apps. I’m happy to talk about your options here, but I recommend that you start a new thread for this because hotspot providers is not the droid you’re looking for. Put your new thread in App & System Services > Networking and tag it with Network Extension. That way I’ll be sure to see it go by. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='866814022, TataChaitanya, /thread/805809?answerId=866814022#866814022, /profile/TataChaitanya'] I am trying this as part of authorisation plug-in only. [/quote] Quoting myself here: [quote='865561022, DTS Engineer, /thread/805809?answerId=865561022#865561022'] There’s no supported way to do this. [/quote] and: [quote='865561022, DTS Engineer, /thread/805809?answerId=865561022#865561022'] My advice is that you file an enhancement request [/quote] I can answer your specific questions, but those answers won’t change this conclusion. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='807782021, RickHedin, /thread/807782, /profile/RickHedin'] I don't understand why. [/quote] Yeah, that’s confusing. macOS has two keychain implementations, the file-based keychain and the data protection keychain. See TN3137 On Mac keychain APIs and implementations for more about this. The security tool puts the password into the file-based keychain. In Keychain Access that shows up in login. The Passwords app is centred around the data protection keychain, and hence doesn’t see it. There is no command-line tool access to the data protection keychain. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='807898021, SadCat, /thread/807898, /profile/SadCat'] plain (non-bundled) executables that request screen recording access no longer appear [/quote] Indeed. I’ve seen reports of this for Full Disk Access — see this thread — but didn’t realise that it was affecting other TCC settings as well. IMO this is a bug and I encourage you to file it as such. When you’re done, post your bug number so that I can associate it with the bugs that originated from the Full Disk Access side of things. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

An API key for what? There are bunch of Apple technologies and services that use API keys, so it’s hard to route your question without the specifics. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This works if you’re using a macOS 15 (or later) guest on a macOS 15 (or later) host [1]. It won’t work for a macOS 14 guest, regardless of the host. In Virtualization Resources you’ll find a bunch of links to resources related to virtualisation for developers, including links to: The Apple Support article that describes the limitations of Apple Account support in the guest. A forums thread that talks about the same. And another forums thread about getting Xcode working in the guest. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] To be clear, the guest must have been created on a macOS 15 host. It won’t work if you: Create the guest on a macOS 14 host and then move it a macOS 15 host Or create the guest on a macOS 14 host and then upgrade your host to macOS 15

[quote='807854021, nikhil2701, /thread/807854, /profile/nikhil2701'] this doesnt use the new structured concurrency. [/quote] Right. It was written before the new API was release and I haven’t updated it yet because most folks who want to do this need to support iOS 18, where the new API isn’t available. Oh, and I haven’t had time |-: [quote='807854021, nikhil2701, /thread/807854, /profile/nikhil2701'] I am particularly interested … TLS with PSK encryption support [/quote] AFAIK that’s not currently supported (r. 159170556)-:. I’d appreciate you filing an enhancement request for that. While we have a bug about it already, it’s an internal bug, and bugs from third-party developers can help in situations like this. Please post your bug number, just for the record. [quote='807854021, nikhil2701, /thread/807854, /profile/nikhil2701'] switching between Wifi and peer to peer interface [/quote] I’m not sure I understand that. Please elaborate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Supp

This is macOS, right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='807744021, HarimaSun, /thread/807744, /profile/HarimaSun'] Does this mean ODR will be deprecated? [/quote] Yes. We said that explicitly in WWDC 2025 Session 325 Discover Apple-Hosted Background Assets. [quote='807744021, HarimaSun, /thread/807744, /profile/HarimaSun'] If so, when will it officially take effect? [/quote] AFAIK there’s no announced timeline. However, the message seems pretty clear to me: It wouldn’t be wise to use ODR in a new product. Note that the above-mentioned WWDC session also introduced Apple-host background assets, which covers much the same territory as ODR. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='807924021, SoumyaMahunt, /thread/807924, /profile/SoumyaMahunt'] Is this approach reliable? [/quote] No. You can disable preview support using a build settings, even in the Debug build configuration. Indeed, that’s something I do all the time. Lemme confirm I understand your requirements: You’re working on a framework. You want to create an XCFramemwork from that. And give that XCFramework to other developers. And then inside that framework you want to check whether the host app was built with the Debug build configuration. Is that right? If so, to what end? And are you sure that you want to check the build configuration? A lot of the time it’s not the build configuration that matters, it’s the way that the app was signed. Or the way that’s it’s run (from Xcode or like a user would). And those questions have different answers. Is this iOS? Or macOS? Or both? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com