“eskimo”

[quote='880412022, hasii2021, /thread/818406?answerId=880412022#880412022, /profile/hasii2021'] I put them [in FB22267132] but not sure if this is correct [/quote] That’s cool. When I open the system log snapshot you included (system_logs.logarchive) I see this: type: default time: 2026-03-17 21:32:51.951555 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: UNIX error exception: 2 type: default time: 2026-03-17 21:32:51.951587 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67068 type: default time: 2026-03-17 21:32:51.951603 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 type: default time: 2026-03-17 21:32:51.951615 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 This seems like an understandable error cascade: The first error, 2, is ENOENT, which is an error commonly returned by the BSD su

[quote='880307022, SurferDog, /thread/818415?answerId=880307022#880307022, /profile/SurferDog'] We kind of expect the permissions to disappear when installing an update [/quote] I don’t know why you have that expectation. If both the old and new versions of the code are signed in the same way, the system should maintain the privilege across the update. TN3127 Inside Code Signing: Requirements talks about the mechanism used to implement that. [quote='880307022, SurferDog, /thread/818415?answerId=880307022#880307022, /profile/SurferDog'] I have filed a bug report: FB22261705 [/quote] Thanks! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880359022, timboudreau, /thread/818192?answerId=880359022#880359022, /profile/timboudreau'] Seems pretty byzantine and fragile [/quote] Yeah. I considered this approach before I replied to you yesterday, but I concluded that: I’m not sure if it’s possible to pull off [1]. And even if it is, it’s likely to be very fragile. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Your appex is sandboxed so: It can’t spawn your app’s executable as a child process because that would require reinitialising the sandbox, something that the system specifically blocks. See App Sandbox Inheritance within Resolving Trusted Execution Problems. It should be able to launch the app with NSWorkspace, but NSWorkspace doesn’t honour all of its configuration when it’s called by a sandboxed process.

[quote='880390022, Abel_Kefan, /thread/819088?answerId=880390022#880390022, /profile/Abel_Kefan'] I realized that I hadn't added the Hotspot Configuration Entitlement [/quote] Oh, hey, would ya look at that. I can reproduce this myself using NEHotspotConfiguration Sample. If I remove the Hotspot capability I get error 8 when attempting to add a configuration. [quote='880390022, Abel_Kefan, /thread/819088?answerId=880390022#880390022, /profile/Abel_Kefan'] I still think it would be better if the error message [provider] a clearer hint to developers [/quote] Agreed. Please file a bug requesting that and then post the bug number here. And now I’m off to update Understanding NEHotspotConfigurationErrorInternal (-: Thanks for sharing this titbit! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880441022, jzilske, /thread/817599?answerId=880441022#880441022, /profile/jzilske'] I was using a wi-fi that basically blocks everything [/quote] Hey hey! And, yeah, I see stuff like that all the time (-: [quote='880441022, jzilske, /thread/817599?answerId=880441022#880441022, /profile/jzilske'] apparently the connection is secured using some sort of pinning [/quote] Interesting. The weird part about this is your suspicion that the traffic is coming from within the web view, but it’s not obvious code running in the web view — so JavaScript, basically — could implement pinning. So, I think it’d be worthwhile double checking the origin of this network connection. With mitmproxy you should be able to get the source IP and port number of the request. And you can then use RVI to track the originating process. RVI puts this in packet metadata, which you can display by running tcpdump with the -k option. See the tcpdump man page for details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technica

You’re code signing your app and app extension, right? There was a very similar report last week that was caused by a failure to sign. [quote='819160021, alexfs123, /thread/819160, /profile/alexfs123'] The logs show the following [/quote] That’s quite hard to read. See tip 5 in Quinn’s Top Ten DevForums Tips for advice on how to post preformatted text. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The PPQ outage from last week [1] was a very specific thing and it’s definitely not related to whatever issue you’re hitting now. [quote='819180021, KW-P, /thread/819180, /profile/KW-P'] Ping still fails [/quote] Testing with ping isn’t helpful in this case; AFAICT ppq.apple.com never responds to pings. Consider: % ping ppq.apple.com PING use1-ppq-ext-prod.sbz.apple.com (17.33.200.235): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 ^C --- use1-ppq-ext-prod.sbz.apple.com ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss % curl -I http://ppq.apple.com HTTP/1.1 301 Moved Permanently … Location: https://ppq-ext.v.aaplimg.com/ If you want to try out the redirect link, you have disable the client’s trust evaluation on the server: % curl -I https://ppq-ext.v.aaplimg.com/ curl: (60) SSL: no alternative certificate subject name matches target host name 'ppq-ext.v.aaplimg.com' … % curl -I --insecure https://ppq-ext.v.aaplimg.com/ HTTP/2 404 … Of course, that

I’ve not heard of widespread problems with iCloud Private Relay on the iOS 26.4 betas, but that doesn’t mean that this problem isn’t real. My general advice on this front is that you file a bug. Or, in this case, encourage your user to file a bug. They can do that using Feedback Assistant. Ideally they’d do that immediately on seeing the problem, so that the sysdiagnose log attached by Feedback Assistant captures the issue in progress. If they do this, ask them to pass the bug number along and then post it here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880415022, ToshiyukiTakeda, /thread/819261?answerId=880415022#880415022, /profile/ToshiyukiTakeda'] Will the Entitlements field for Team ID NWKYYYYYYY be added if I simply wait? [/quote] Our records show that Team ID NWKYYYYYYY already has access to the entitlements need to use NEAppPushProvider. In Xcode’s Signing & Capabilities editor, it should show up as Network Extension (additional values). Likewise in the App ID editor on the Developer website. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There’s no general-purpose way to get Wi-Fi scan results on iOS. Depending on your specific scenario, there may be special-purpose ways to achieve your goals. TN3111 iOS Wi-Fi API overview has more about that. Please read that 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

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

ZiZU_Inc, I’m not privy to the details of your case but, even if I were, I wouldn’t be able to discuss it. I’m replying here for the benefit of anyone else who stumbles across this thread. The Team is not yet configured for notarization error is not 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. 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. [quote='880393022, shaneholloman, /thread/819152?answerId=880393022#880393022, /profile/shaneholloman'] now notary service is resolved. [/quote] Cool. [quote='880429022, HuangKun, /thread/819152?answerId=880429022#880429022, /profile/HuangKun'] 24 hours later, problem alive.... [/quote] OK. My experience is that this “in-depth analysis” clears by itself, usually after a day or two, and that’s exactly how it panned out for shaneholloman. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='863282022, Dirk-FU, /thread/771129?answerId=863282022#863282022, /profile/Dirk-FU'] Any news about Support for Swift 6.2 and iPadOS 26? [/quote] Swift Playground 4.7 shipped yesterday. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Just to close the loop on this: [quote='872091022, DTS Engineer, /thread/812429?answerId=872091022#872091022'] We do hope to ship an update to the Swift Playground app [/quote] Swift Playground 4.7 shipped yesterday. Too late for the challenge, alas, but good news nonetheless. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com