“eskimo”

premak, I will respond in the your specific thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='818649021, emishin, /thread/818649, /profile/emishin'] I have 6 submissions spanning from March 4 to March 10, 2026, and none of them have completed [/quote] I strongly suspect you’re hitting the “in-depth analysis” case; see my standard spiel about this below. However, that normally clears after a few days and this has been a lot longer than that. I’ll check on it and get back to you. 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 in-depth 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.

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth 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

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

A few brief clarifications and comments: I am seeking clarification on whether the various driverkit entitlement families (com.apple.developer.driverkit.family.*) are available for development on my local Mac without requesting entitlements from Apple. Making the more explicit, they Development Only entitlement variants do two things: They match against a VERY broad hardware configuration, basically letting you match any hardware. Their ONLY available to Development signed builds. Note that the second criteria heavily restricts distribution, as development builds will ONLY run on machines which were registered with your developer account at the point the signing profile was generated. This is largely invisible when using automatic signing (Xcode will just generate a new profile), but can be easy to overlook with manual signing. At WWDC2022 Apple stated that In MacOS... In fact, all DriverKit family entitlements are now available to use for development. On these very forums, Eskimo himself also sugges

You should definitely file a bug against the App Store validator. There’s nothing fundamentally wrong with using square brackets in your app name. Please post your bug number, just for the record. On the workaround front, the idea of setting your app’s on-disk name to something without the square brackets and then applying the square brackets at the display level seems reasonable. However, it’s not as simple as setting CFBundleDisplayName. Rather, you have to go through the localisation subsystem. macOS does support localised app names but there are complications: The bundle name (CFBundleName) must match the file name on disk (without the .app extension, obviously) [1]. If they do match, it checks for LSHasLocalizedDisplayName. And if that’s set, it tries to get the localised version of CFBundleDisplayName. Note There are further complications related to CFBundleDisplayName, but I didn’t explore those in depth. My goal was just to get anything to work (-: So, consider this app: % plutil -p Test817684_3.app/C

[quote='879525022, dispacthMain, /thread/818199?answerId=879525022#879525022, /profile/dispacthMain'] Do you think standard DNSSettings still should work? [/quote] I don’t know, which is why I suggested you try it. It’s definitely counter-indicated by the docs, but I can’t see anything in the code that blocks it. OTOTH the system is complex, so it’s easy for me to miss things. Of course, if it does work then there’s the question as to whether you should relying on this implementation detail. However, it’s only worth digging into that if it actually works. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='879551022, parker9, /thread/810258?answerId=879551022#879551022, /profile/parker9'] A user was reporting the crash which I could not reproduce locally. [/quote] A crash? bwill’s original report was about a hang. Are you using “crash” in the general sense? Or is it actually crashing? If so, please ask your user for crash report and post it see. For advice on how to post a crash report, see Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='879587022, jblum2000, /thread/817268?answerId=879587022#879587022, /profile/jblum2000'] The first problem is that the entitlements validated flag is not set. [/quote] OK. That explains the runtime behaviour you’re seeing, because: The system won’t grant you access to the container because it can’t trust your entitlements. And it won’t display the standard UI because it knows that file providers run in the background. [quote='879587022, jblum2000, /thread/817268?answerId=879587022#879587022, /profile/jblum2000'] And the codesign result shows that the new app group is not present [/quote] And that’d do it. As to how it got built this, it’s hard to say without digging deeper into your build process. [quote='879587022, jblum2000, /thread/817268?answerId=879587022#879587022, /profile/jblum2000'] I'll try a complete rebuild and get back to you ASAP. [/quote] That’s always a good start. And if that doesn’t help, you can look at the build transcript to see how entitlement values are flowing from your .entitle

[quote='879601022, tim_the_bear, /thread/818398?answerId=879601022#879601022, /profile/tim_the_bear'] So this seems to be a delay on new organisations [/quote] We don’t officially document the criteria that trigger “in-depth analysis”. Furthermore, I won’t explain why that is (although it’s not hard to speculate :-). Anecdotally, many of the threads I see here on the forums are from folks with a new team. However, I have seen cases, like this one, where long-standing developers bump into it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the download link. I’m not sure what the actual problem is here. I ran your app through (roughly) the process described in Testing a Notarised Product, and everything seemed to work just fine. Specifically: In a fresh macOS 26.3.1 VM, I downloaded that zip archive in a way that sets quarantine. I unpacked it using the Finder. And then I opened the app using the Finder. It passed Gatekeeper, launched, and showed its initial UI. I then ran some basic validity checks, and those also passed with flying colours: % syspolicy_check distribution umldiagrammer.app App passed all pre-distribution checks and is ready for distribution. % codesign -v --deep --strict -vvv umldiagrammer.app … umldiagrammer.app: valid on disk umldiagrammer.app: satisfies its Designated Requirement % spctl -vvvv --assess --type exec umldiagrammer.app umldiagrammer.app: accepted source=Notarized Developer ID origin=Developer ID Application: Humberto Sanchez II (NA8Z96F8V9) Please run through these steps yourself and let me know what

[quote='879446022, Nickkk, /thread/817724?answerId=879446022#879446022, /profile/Nickkk'] how does the original story continue? [/quote] Now you have: A Mach-O image UUID Its load address And a crashing address within that image This allows you to: Symbolicate the crashing address manually, as explained the Symbolicate the crash report with the command line section at the end of Adding identifiable symbol names to a crash report. If necessary, disassemble the code to get a firm handle on how the referenced source code manifests in your app. Correlate that with the register state from the crash report. There’s no guarantee that this will yield anything useful though. The fact that: You hit a memory access exception while fetching instructions And the weird structure of the crash report suggests that something was really borked with that process, and it’s hard to investigate such borkage without a reproducible case, or at least a sysdiagnose log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Techni

[quote='879476022, pjfloyd, /thread/811043?answerId=879476022#879476022, /profile/pjfloyd'] at least on 12 and 13 Intel. [/quote] Does that mean you only tested in on macOS 12 and 13? Or that you tested it on newer systems and things were better there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='631502022, DTS Engineer, /thread/659052?answerId=631502022#631502022'] the Mach service provided by the NE side takes precedence. [/quote] This changed in macOS 11. See this post for the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com