“eskimo”

[quote='905258022, RomainDropB, /thread/843546?answerId=905258022#905258022, /profile/RomainDropB'] it's purely a matter of reassigning the existing approved config to the correct team. [/quote] … and waiting for that to be onboarded. Previously the wrong team was approved but not onboarded. FB24607828 is a request to transfer the approval to the right team, but it still has to wait for onboarding. That can take a while. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for bringing this to the forums. I read through your post a couple of times and I’m still not sure I understand your issue. Most folks in your situation simply spawn the child process (via fork/exec*, posix_spawn, NSTask, Process, or Subprocess). Then one of two things happens: If the child terminates first, the parent reaps it. If the parent terminates first, the child gets reparented but that’s fine because eventually the child will terminate. It sounds like you’re concerned about the parent terminating and then the child getting stuck, resulting in no one being around to clean up. Is that right? Or have I misunderstood something? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You attached a sysdiagnose log to your bug but it looks like that log was from macOS 15.7.9. Please reproduce the problem on macOS 27, immediately grab a sysdiagnose log on that Mac, attach it to your bug, and then reply here when you’re done. ps I have lots of bug reporting hints and tips in Bug Reporting: How and Why? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You added the CallKit tag to your thread but reading your post it doesn’t look like you’re using CallKit. Rather, you’re opening the default phone app via a tel URL. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Please post an example crash report, preferably one in JSON format. Posting a Crash Report has instructions on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for additional analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='845783021, mathpoem, /thread/845783, /profile/mathpoem'] four days with no movement, including on a 14 KB binary, seems beyond the usual delay. [/quote] That’s longer than normal, yes, but it’s not completely unprecedented. If your requests are still stuck after a week, reply here and I’ll take a proper look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for bringing this to the forums. I need to do research this before I can give you a definitive answer. I’ll reply here when I know more. ps For those following along at home, note that this came up in other thread but we never drove it to a conclusion there, so I’m gonna use this thread to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='845980021, fortens-dev, /thread/845980, /profile/fortens-dev'] are these independent conditions that must both be satisfied by the calling process? [/quote] Yes. Note that the partition list is… well… a list, and it’s satisfied if the calling process matches any entry on that list. I think that means that you can achieve your high-level goal, but it’s hard to offer guarantees because, yeah, access control in the file-based keychain has a lot of weird legacy edge cases. [quote='845980021, fortens-dev, /thread/845980, /profile/fortens-dev'] I’m specifically looking for the supported contract here. [/quote] I’m reluctant to make any promises here. As I mentioned above, access control in the file-based keychain is complex. Moreover, it’s changed in the past (partition lists were introduced in, what, 10.12?) and it could change again in the future. Keep in mind that the file-based keychain is effectively deprecated. See TN3137 On Mac keychain APIs and implementations for more about that. However, it’s also

Are you working on the same product as this person and this person? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

My “thin compatibility ice” comment refers to this entire task. To escape that you’d have to not use Mach messaging directly, and you’ve already established that that’s a requirement. To give you a better answer I need more information about this: [quote='905142022, GustavoBataller, /thread/845644?answerId=905142022#905142022, /profile/GustavoBataller'] For a security boundary in a product intended to ship to users [/quote] What sort of product is this? Why high-level goal are you trying to achieve? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Two questions: Have you already migrated the App ID? Is the code that generates the “separately migrated data” already in the app that’s currently in the App Store? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yeah, sorry about the delay on my side. I’ve been in and out of the office this past month. Looking at FB24607828 I don’t see anything to be concerned about. PIR onboarding takes time, even for normal requests. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='905115022, franck44, /thread/845286?answerId=905115022#905115022, /profile/franck44'] My question is specifically whether Apple provides any carrier-specific [/quote] This isn’t something I can answer. See this reply for an explanation. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

At a technical level, I don’t see anything that stops you doing this. If you enable the hardened runtime (which you should :-), you’ll need to disable library validation because the plug-in won’t be signed by you. You’ll also need to dynamic extend your sandbox to allow access to the bundle, including its main executable. Typically you do that using the open panel, and persist that access using a security-scoped bookmark. After that, use your dynamic loading API of choice (NSBundle, CFBundle, dlopen) to load the bundle’s executable and call code in it. I prototyped this here in my office and it worked a treat. I’ve pasted in some code below. I tested this with Xcode 26.6 on macOS 26.6.1, but I don’t think this story has changed since the very early days of the App Sandbox. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com This is the code within my bundle: @c func entryPoint() { print(Hello Cruel World!) } Note It uses @c, as

We can’t help you with questions like this here on the Apple Developer Forums. The forums are primarily focused on the APIs in Apple’s various platform SDKs and, as you’ve noted, most of the information you’re looking for is not available via those APIs [1]. There may be more options available to carriers, but that’s not something I maintain expertise in and, even if I did, I’m only able to discuss publicly documented stuff. If you’re working on behalf of a carrier, I recommend that you escalate this via your carrier’s contact at Apple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Indeed, some information that was previously available is no longer available.