“eskimo”

[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

Thanks for filing FB22189729. [quote='879085022, DTS Engineer, /thread/817488?answerId=879085022#879085022'] I’m going to talk to some colleagues [/quote] Based on that discussion, I think I’m gonna let my original recommendation stand, that is, add a dummy use of Subprocess within your app. It’s a bit kludgy, but it’ll get the job done. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='879236022, ADietz, /thread/817792?answerId=879236022#879236022, /profile/ADietz'] each needs some level of code modification of the app under test? [/quote] No, and yes. The first approach doesn’t require you to modify the app under test because the actual local networking ends up being done by your Mac. However, it’s a lot trickier to set up because it requires you to bring up a non-local server. The second approach is easier to set up but it does require support within the app under test. Hmmm, and that suggests a third approach, which is a variant of the second one but with the proxy running in a completely different app on the test device. For this to work you’d have to ensure that this proxy app runs indefinitely in the background. That’s tricky to do in production — see iOS Background Execution Limits — but you can probably make it work in this just-for-testing scenario. So, something like this: Create an ‘audio streaming’ app that continuously plays silent audio and implements the sort of netwo

[quote='879430022, dispacthMain, /thread/818199?answerId=879430022#879430022, /profile/dispacthMain'] I looked up documentations and could not find any payload to always apply search domains [/quote] Yeah, I think you’re right. I only deal with configuration profiles tangentially, and I just assumed that this would be possible. The experts on this tech lurk over in Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area, so you could try asking there. Just for my own education, did you try the NEDNSSettingsManager approach? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is confusing. There are different types of ‘bridging header’. The actual bridging header lets you call Objective-C from Swift, but there’s another header that you use to call Swift from Objective-C. I believe you’re looking for the latter. If so, I have a step-by-step example of this in this post. I just retested this with Xcode 26.3 and it continues to work as described. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com