“eskimo”

The person on this thread had a similar issue and found a solution for it. I’m not sure if you’re hitting the same issue, but I figured it’d be worth you checking. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Excellent news. Thanks for closing the loop here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you using Xcode to build an app? If so, I recommend that you enable automatic code signing and let it take care of this complexity. My experience is that it’s extremely effective in modern versions of Xcode. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='848396021, rasakhodavirdilou, /thread/848396, /profile/rasakhodavirdilou'] I have submitted the full crash reports … under FB24937933. [/quote] Thanks. That’s the right path forward for issues like this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='848364021, fix_parrot, /thread/848364, /profile/fix_parrot'] Filed as FB24933164. [/quote] Thanks. That’s generally the best first step when you encounter a compatibility problem on a beta release. I looked at your bug and there’s no sysdiagnose log. Please reproduce the issue, then trigger a sysdiagnose log, and then add it to the bug. See Bug Reporting > Profiles and Logs for more information about sysdiagnose logs. Also, I want to make sure you’ve made the change described here. It shouldn’t be necessary on the 27.2 beta, but it’s something you’ll have to do soon so you might as well do it now. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to clarify the issue here. Where are these times being displayed? In your app? If so, what API do you use to display them? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Also, I have some screenshots in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First up, thanks for all those bug reports FB24895271, FB24895264, FB24895282). Much appreciated! Second, regarding your workaround, I asked around internally and it seems reasonable enough. We’re not aware of any specific negative consequences for having an interface instantiated but doing nothing. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Just a quick follow-up here. macOS 27 introduced an alternative approach for third-party developers to sandbox child processes, namely the es_new_descendants_client mechanism within Endpoint Security. If you find yourself reaching for sandbox-exec and custom SBPL code — techniques that are, as I mentioned above, unsupported by DTS — you should consider that alternative. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for all that info. I did some digging and my best guess is that Codex is applying a custom sandbox, using sandbox-exec and their own SBPL code. We don’t support that, for the reason I explain in this thread. Given that, there are limits to how much I can help you here. I suspect that your JAX code is inheriting this custom sandbox from Codex, and that’s the root cause of this problem. And that has a couple of negative consequences: I can’t help you with your problem, because I’ve no idea how Codex has set up this sandbox. I normally encourage folks who are having problems like this to contact their tooling vendor and, if necessary, the tooling vendor can seek help from Apple. However, that won’t work in this case because we can’t help them with SBPL [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Our advice for folks who want to implement custom sandboxing is to lean in to the es_new_descendants_client API w

[quote='906868022, Alihan1, /thread/847615?answerId=906868022#906868022, /profile/Alihan1'] its embedded XPC service before the service sends its first message [/quote] Hmmmm, this question seems backwards to me. An XPC service is launched in response to an XPC message on its named endpoint. So are you worried about the service sending its reply to that message? Or about the service talking to some other XPC service while processing that first message? The way you’ve phrased this question is very reminiscent of this thread, where the developer was trying to sandbox a child process. And my advice for those folks was to lean in to the new es_new_descendants_client feature. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='906880022, nathan-pierce-veertu, /thread/845455?answerId=906880022#906880022, /profile/nathan-pierce-veertu'] Wow you're right. [/quote] *phew* You had me worried there for a minute (-: [quote='906880022, nathan-pierce-veertu, /thread/845455?answerId=906880022#906880022, /profile/nathan-pierce-veertu'] Regardless, I need to know the legal [/quote] Sorry, but I can only help you with technical stuff. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is definitely a ‘just because you can doesn’t mean you should’ moment (-: [quote='848220021, zosoz, /thread/848220, /profile/zosoz'] What are the XNU devs planning on doing with them? [/quote] To be clear, we can’t talk about The Future™ here on the forums. See tip 3 in Quinn’s Top Ten DevForums Tips. However, you can see this feature already being used by the Objective-C runtime. Which brings me back to my original point. While this is technically API, you’d want to think very carefully before using it in a product that you ship to a wide range of end users. The Objective-C runtime has the advantage that it’s built in to the system, so if the system changes in a way that breaks this API it can adapt. In contrast, any third-party products in the same situation would require an urgent, and potentially very difficult, update. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

IMO this is Just A Bug™, and I encourage you to file it as such. Fortunately the workaround is super easy (-: Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com