“eskimo”

[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

[quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] I wanted to confirm that this is the current best practice. [/quote] For an ES sysex, yes. As to what happens when you combine ES and NE, I did some digging and that text is definitely present in the Xcode 12.5 man page and definitely gone in the Xcode 13 one. Based on that info I was able to track down FB8701548, which was a developer request that we remove that limit. This was resolved in macOS 11 and, as part of that, we removed that text from the man page. Neat! With that in mind, let’s return to your other questions: [quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] should they each declare the Mach service name under their respective Info.plist keys? [/quote] That’s up to you. I can see arguments either way: If the ES and NE subsystems within your sysex are tightly bound together, it’d make sense to use a single named endpoint. OTOH, if those subsystems act independently, it’d make sense to have two d

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

[quote='818599021, siddhant-mac, /thread/818599, /profile/siddhant-mac'] Could you clarify whether the attestKey flow involves sending attestation data to an Apple server [/quote] What’s the background to this question? I mean, why does this matter to you? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are multiple technologies under the iCloud banner, and the error your posted only shows the start of the entitlement name (com.apple.developer.icloud-) so it’s hard to know which one you’re shooting for. So, some questions: Do you have automatic code signing enabled? It can generally fix problems like this… automatically. Did you enable this via a capability in the Signing & Capabilities editor? If so, which one? 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

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

[quote='879071022, asantoni64, /thread/785730?answerId=879071022#879071022, /profile/asantoni64'] it seems that QWAC support is still not operational [/quote] I checked on this and you are correct. [quote='879071022, asantoni64, /thread/785730?answerId=879071022#879071022, /profile/asantoni64'] one wonders what the problem is in making it operational... [/quote] Sadly, I have to leave you wondering. I continue to have no info to share on that front. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, that was exciting |-: [quote='879472022, simonsruggi, /thread/818403?answerId=879472022#879472022, /profile/simonsruggi'] It looks like Apple fixed the issue. [/quote] Yep. I can’t really go into details here, other than to say that: ppq.apple.com is a service on the critical path for the trusted execution of code in some situations [1]. It was having problems. Those are now fixed. I don’t have time to read through all 10 pages of posts on this thread. So, if there’s something you want to draw my attention to here, I recommend that you start a new thread with the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There might be more info about it on the enterprise support side of things, but the only developer-focused reference I could find for it was in an old Xcode help page: Manually trust a developer on iOS.

I’m not sure what’s going wrong here but I have a couple of diagnostics tests for you to run. Both require you to get your file provider started. Once you have that: Use launchctl procinfo to check whether the process has the entitlements validated flag set. App Groups: macOS vs iOS: Working Towards Harmony has an explanation of how to do this. Use codesign to check the entitlements of the running process: % codesign -d --entitlements - PID where PID is the process ID. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Earlier I wrote: [quote='878084022, DTS Engineer, /thread/817516?answerId=878084022#878084022'] it certainly looks like this includes Device Activity report extensions. [/quote] I was digging into this some more in a different context, and as part of that I found a clear explanation of how this works. See the doc comments for DeviceActivityReport. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com