“eskimo”

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

I don’t have any info to share beyond what you can see in Feedback Assistant: Your bug, FB13845934, remains unresolved. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

That message corresponds to errSecCSInvalidObjectRef (-67071). That’s an obscure one. I’ve been supporting Mac coded signing for almost a decade and I’ve never seen it before. Well done! [quote='818406021, hasii2021, /thread/818406, /profile/hasii2021'] Can't figure out how to post the log file. [/quote] You can post log files as text attachments. I have info on how to do that in Posting a Crash Report. Its focus is on crash reports, but the process for posting a text attachment is the same in both cases. However, the notary log is unlikely to help here because, as you say, the app notarises successfully. Rather, this is a code signing error on your local Mac. [quote='818406021, hasii2021, /thread/818406, /profile/hasii2021'] when I try to verify the signature I get the above error. [/quote] How are you doing that? Normally I’d verify a signature like so: % codesign -v --deep --strict /path/to/my.app Is that what you’re doing? As to the potential causes of errSecCSInvalidObjectRef, there are very few. Most of

My general approach for problems like this is to set up a VM that’s never seen my product before and then use that VM to test various user-level sequences. For example, I might install version N of the app, check that screen capture works, then install version N+1, and then check that it continues to work. The advantage of doing this on a VM is that you’re starting from a fresh machine and you can save and restore snapshots for your various tests. If your product passes those tests, and thus works in general, this becomes a question of what’s happening on specific user machines to cause the reported issue? That’s a much harder question to answer. macOS has lots of flexibility — with the user able to install and remove apps at will, install multiple copies of your app, and so on — and that flexibility causes serious challenges for TCC. There’s no easy way to map from specific symptoms back to the root cause. However, it’s unlikely to be your app’s issue. I mean, there’s nothing you can do at the code level to

[quote='879421022, Arihant_Marwaha, /thread/818407?answerId=879421022#879421022, /profile/Arihant_Marwaha'] its resolved now [/quote] Cool. Thanks for closing the loop. And just FYI, I suspect you were being hit by an infrastructure outage yesterday. Based on the posts at the end of this thread it seems to be resolved. It’s just unfortunate that you happened to see it after updating to the latest beta. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

How reproducible is this crash? Can you reproduce it reliably in your office? Or are you chasing bug reports coming in from the field? Also, if you put that code into a small test project and run it with the standard memory debugging tools, does it crash there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Jweeces, I don’t think you’re hitting exactly the same problem as Tonnew. Rather, I think you were being hit by an infrastructure outage yesterday. Based on the posts at the end of this thread (10 pages, wow!) it seems to be resolved. Reply back here if you continue to have problems. @Tonnew , Sorry I missed your thread the first time around (I suspect I was out of the office). I you continue to have problems with this, please post an update here and I’ll take a look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com