“eskimo”

This question confused me because you folks are convinced that an Install on this iPad button should exist but I’ve never seen such a thing. So I ended up seeking advice from the Swift Playground team. They confirmed that, while such a button does exist on the Mac — it’s called Install on this Mac — there is not, and has never been, such a button on iPad. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

D’oh! There was a typo in my Markdown [1]. I’ve fixed that now. Thanks for the heads up. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] In my defence the link worked in the preview, only failed once the reply was posted. That’s obviously a bug in our forums platform. I’ll need to go investigate that. I think we might’ve fixed it already.

[quote='909509022, endecotp, /thread/850144?answerId=909509022#909509022, /profile/endecotp'] Here's what I'm actually doing: [/quote] Sadly, I don’t have any easy solutions here )-: If you try to display a path and include file names as they’re shown by the Finder then either: You use a slash as the separator, whereupon the user can’t distinguish those slashes and the ones in the file names. You use a colon as the path separator, which is staggeringly old school. The way the Finder gets around this is to not render paths in the Posix style. You can see this in its path bar (View > Show Path Bar) and I think that’s also supported by NSPathControl. When it comes to creating files, the only good way to know whether a name is acceptable is to try creating a file with that name. You can do various bits of preflighting — ban slashes, nul characters, leading dots, and so on — but nothing will give you 100% accurate results in the general case. Given this reality, you’ll have to make some sort of compromise, and

[quote='909483022, rbmanian75, /thread/850614?answerId=909483022#909483022, /profile/rbmanian75'] I mean both [/quote] OK. I think you’re being bitten by the com.apple.security.inherit oddity that I discuss here. [quote='909483022, rbmanian75, /thread/850614?answerId=909483022#909483022, /profile/rbmanian75'] but however withtout the microphone entitilements the recoding works. [/quote] Do you have these entitlements on the app itself, that is, the parent that spawned the helper child? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='909339022, Brian_Rucker, /thread/849029?answerId=909339022#909339022, /profile/Brian_Rucker'] SessionGetInfo(audit_asid, ...) does not return within a 15-second observation window. [/quote] Wha!? That’s strange. As I mentioned early, SessionGetInfo is effectively a kernel call these days. If you run sample against the stuck process during this interval, what does the backtrace look like? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve written the following as a general response. So, pawanquantum, this applies to you, but it also applies to anyone else who has created, or is thinking about creating, an authorisation plug-in. Authorisation plug-ins are in a very parlous state. Honestly, I consider them to be deprecated, and I’m hoping that we formally deprecate them at some point (r. 190103576). Given that, my general advice is that you not implement one. If you’re an identity provider looking to integrated with macOS, Platform SSO is the obvious path forward. If that’s missing a feature you need, please do file an enhancement request against it. If you’re planning to use an authorisation plug-in for some other task, try to find an alternative. If you can’t find an alternative, file an enhancement request that describes what you’re trying to do, how you’re implementing that with an authorisation plug-in, why none of the existing alternatives work for you, and roughly what you’d like to use instead. And if you do file an ER, please reply

What’s your actual goal here? You’ve described a very complicated system that ultimately boils down to this: [quote='851167021, laoblin, /thread/851167, /profile/laoblin'] Query checks a synthetic target process’s identity using Security.framework and produces a fixed 28-byte result. [/quote] You could just as easily do that without the additional processes, so I suspect that isn’t the actual goal, but rather that there’s some bigger picture. That matters because it seems like you’re micro-benchmarking the performance of posix_spawn, which isn’t a very useful activity. macOS has never been a speed demon (daemon :-) when it comes to starting new processes, and there aren’t really any optimisations you can apply to it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not actually sure what you’re looking for here. In that other thread I was pretty clear that changing your BSD credentials puts you in an weird space, and it’s very hard to offer guarantees as to what will actually happen in that space. There’s certainly no documentation about the behaviour of macOS at this level. You are very much in implementation detail territory here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve been talking to a different developer about a similar issue and I think my reply this morning answers your question. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='909293022, primetimeindy, /thread/850727?answerId=909293022#909293022, /profile/primetimeindy'] One specific question question about library constraints [/quote] Now that’s something I can answer (-: The dynamic linker works in phases. It first tries to resolve all the dependencies, then connects up the imported symbols, then calls the initialisers. If the process loads A which then imports B, it’ll fail at the first step. That’s because in order to determine a library’s dependencies it has to look at the library (that’s where the LC_LOAD_DYLIB commands exis). So it maps A and looks for its dependencies, then tries to map B to look for its dependencies. The second mapping fails due to library constraints, and that causes the entire import to fail. Another way to think about this is that the dynamic linker runs initialisers from the bottom up. In order to run A’s initialiser, it has to see if B has an initialiser. But it can’t do that because it can’t map B. This is more than just an implementation det

You mean com.apple.security.device.microphone, right? Because there’s the confusingly similar com.apple.security.device.audio-input |-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='909180022, Scana, /thread/829454?answerId=909180022#909180022, /profile/Scana'] unfortunately we're still seeing this on both iOS 27 and 27.1 [/quote] Bummer. That crash report doesn’t look like it came from Apple. Do you have an Apple crash report for this? I’m specifically looking for one in JSON (.ips) format (see Posting a Crash Report). FWIW, I took another look at that bug and, yeah, we definitely made fixes and they are definitely in iOS 27. My only conclusion is that there’s some other cause for this crash. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for that. I’m not sure what’s going on here, but I do nevertheless have a suggestion. You can help your bug get traction by adding a sysdiagnose log to it. Specifically: On a test device, install the Network Diagnostics and VPN (Network Extension) debug profiles. See our Bug Reporting > Profiles and Logs page. Reproduce the issue, noting down the time. Immediately trigger a sysdiagnose log. Add that to your bug report, along with the timestamp from step 2. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, let’s break this down into two cases: The host app works. The host app fails. If the host app is working then the rules are simple: By the time the guest stops… it’s stopped. There may be cases where that doesn’t happen, see this thread for example, but I’d consider those to be bugs. If the host app fails, it crashes for example, then the system will clean up on its behalf. Again, if that doesn’t happen then that’s Apple’s bug to fix. However, there are no guarantees about the timeline for that. The API has no way to get some of meta handle to the guest, so that a replacement host app can get that meta handle [1] and ask the system whether that guest is completely done. If you’d like us to add support for something like that then please do file an enhancement request for it. Make sure to include detailed info about your requirements, along with info about the high-level goal you’re trying to address. If you do file an ER, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo

I can’t discuss things beyond what you already know: There is a pilot programme running. That web form lets you register your interest, so we can notify you when things change. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com