“eskimo”

There’s no supported way to read the kSecAttrAccessControl property. Even if you could get back at SecAccessControl object — and I’m not sure that’s true — it has no getters. I’m pretty sure I cover that in SecItem: Pitfalls and Best Practices… oh… well… kinda. Check out the Add-only Attributes section. Given that, there’s really only one useful thing you can do with kSecAttrAccessControl, namely, configure it when creating an item using SecItemAdd. For most folks that’s sufficient, because they know how they created the item because… well… they created it. The only time this breaks down is when you have multiple versions of your app and they use different access control settings. In that case I think your best option would be to use some other attribute, like kSecAttrService, to ‘version control’ your use of this property. You should feel free to file an enhancement request for better APIs for this. And if you do, please post your bug number, just for the record. [quote='849755021, sheishman, /thread/849755,

This isn’t something we can help you with here on the forums. Rather, you need to seek help via official channels. For the details, see this post. [quote='849745021, ZeroCAD-dev, /thread/849745, /profile/ZeroCAD-dev'] Developer Support case 102939827032 [/quote] That case number indicates that you’re connected with the right folks, and I encourage you to strive for a resolution via that path. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, I’m glad we ruled that out. And with that, I have a question and a request. Are these files stored on an Apple file system? That is, APFS or HFS Plus? And in a location that’s not shared by a cloud sync service? This includes third-party ones, but also iCloud Drive, and specifically the Desktop and Documents folder when you have synching enabled (per System Settings > YOUR_APPLE_ACCOUNT > iCloud > Drive > Desktop & Documents Folders). I’ve seen cases like this where the underlying cause was a file system problem. Your earlier tests put a limit on how this problem could be expressed, but I still wanna rule this out completely. Earlier you wrote: [quote='907965022, marucello, /thread/849002?answerId=907965022#907965022, /profile/marucello'] three verification tests [failed] with: code or signature have been modified [/quote] If you run codesign with the -v flag, it should tell you what was modified. For example: % codesign -v --deep --strict -v QProcessDock.app QProcessDock.app: valid on dis

I’m glad to hear you’re making progress [1], and thanks for sharing that revocation tip. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For those following along at home, OneMoreBuild had their own thread about this issue.

[quote='907992022, mtnview, /thread/733510?answerId=907992022#907992022, /profile/mtnview'] I need this with sudo. [/quote] At this point I think it’s safe to assume that: This facility was removed… Because of security concerns… And thus it’s not coming back. So, you have a couple of options: Disable SIP Find another path I encourage you to do the latter because disabling SIP is very risky. Speaking personally, I only disable SIP on machines I don’t care about, typically VMs that I’m using for testing. If this is a machine you do care about, then disabling SIP is a bad idea. As to what that other path might be, that’s hard to say without more information about your circumstances. If you’d like a specific suggestion, reply back with more details about what you’re trying to do. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So you’re specifically concerned with the copy of Python installed by the Command Line Tools package? That is, the Command Line Tools package that folks download from our Developer > Downloads > More Downloads page? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve been zenning on the wider issue over the past few days and I’ve had an Idea™ (-: It’s clear that your test suite is really good and finding corner cases in our ‘behaves like a Unix-y system’ story. Given that, it’d be cool if we ran it internally, with the goal of finding and fixing such problems before we start seeding. Do you think that’s feasible? [1] If so, I’d appreciate you filing a enhancement request for just that [2]. I can’t make any promises here — at this point this is just my own off-the-wall idea — but it’s worth a short. Once you’re done, reply here with your bug number so I can add my own (internal) comments to it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Considering things like: All the code is open source Under a reasonable licence And doesn’t require any particularly onerous setup [2] Make sure to include some basic info, covering the sorts of points that I raised in the previous footnote.

[quote='908003022, skywind, /thread/849472?answerId=908003022#908003022, /profile/skywind'] It would also be nice if Apple documents [/quote] Well, it’d be better if we added the NS_SWIFT_SENDABLE macro to the header so that the Swift compiler could do the right thing. If you’d like to see that happen, I encourage you to file a bug along those lines. And if you do that, please post your bug number, just for the record. As to why the old sample code works, that’s almost certainly because it’s compiling in the Swift 5 language mode. That mode will report warnings about Swift concurrency problems that it detects, but: Those are warnings, not errors. It doesn’t insert the runtime traps that detect cases like this. If you switched your project to the Swift 5 language mode then these crashes go away. But that’s not the right solution to this problem because: The goal of the Swift 6 language mode is to flush out assumptions like this, so that you can apply the correct fix. It could potentially turn this nice determi

Thanks for filing FB25068610. [quote='908001022, floorish, /thread/849177?answerId=908001022#908001022, /profile/floorish'] Please let me know if you need more information. [/quote] If we do, it’s most likely we’ll reach out via Feedback Assistant. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Error -26276 is errSecInternal [1]. There are two ways to learn more about this: You can rummage through the Darwin source to look for all the places it’s raised. You can monitor the system log to see what gets logged immediately before you get that error. See Your Friend the System Log for lots of hints and tips on that front. However, I’d like to take a step back here. Your post suggests you’re working with trust objects (SecTrust), and that’s somewhat unusal when dealing with code signing. Is there a reason you’re not working with SecCode? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Per the Darwin source.

[quote='849690021, keremerkan, /thread/849690, /profile/keremerkan'] 1- Is there anything else I need to do to get case 102953576372 completed … ? [/quote] I can’t really answer that. This case is being handled by DevPrograms and I don’t have visibility into it. However, my experience helping other developers in this case is that the answer is “Nothing other than wait.” [quote='849690021, keremerkan, /thread/849690, /profile/keremerkan'] 1- Is … a better route to escalate it? [/quote] No. [quote='849690021, keremerkan, /thread/849690, /profile/keremerkan'] 2- Is there any way to ship a Mac App Store build for these App IDs before the migration … ? [/quote] No [1]. I’ve helped a bunch of developers down this path over the years and it does work, but it can take a while for DevPrograms to enact the change. FWIW, the main gotchas here are: Keychain access — See App ID Prefix Change and Keychain Access. App extensions — If your app has app extensions, make sure to request that they be migrated as well. Rebuild —

Hmmm, this is the third time I’ve seen this question in the last few weeks. Clearly there’s something in the water. Anyway, please read this thread and then reply back here if you have follow-up questions. 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='849561021, pkhor, /thread/849561, /profile/pkhor'] 07701908-cfc9-416b-93d8-783b50cb25c2, created 2026-09-29T18:11:38Z [/quote] Is this still stuck? If so, please run the notarytool info subcommand with that request ID and post the results here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You’ve almost certainly encountered my standard spiel about this, but I’ve included it below just for the record. [quote='908058022, JoyArchivist, /thread/849571?answerId=908058022#908058022, /profile/JoyArchivist'] but after three days [/quote] My experience is that this is longer than usual for the additional analysis path, but certainly not something completely beyond the pale. If this hits the week mark, reply back here and let me know. 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.