“eskimo”

Let’s focus this discussion in your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion in your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The accessibility folks would greatly appreciate it if you stopped creating all your threads in the Accessibility & Inclusion > General subtopic. The correct subtopic for Network Extension questions is App & System Services > Networking. I’ve moved this, and also a bunch of your older threads, but I’d rather spend my time on more productive stuff. For more on this, see tip 4 in Quinn’s Top Ten DevForums Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='879514022, KayleeSC, /thread/791352?answerId=879514022#879514022, /profile/KayleeSC'] What exactly does the failed to register with PIR error mean? [/quote] It’s hard to say without more information. That log entry is recorded by NE when it fails to register with some underlying infrastructure. That registration mechanism follows standard Objective-C error conventions, that is, it has a method result and if that indicates an error, by returning NO, there’s an ‘out’ error parameter. NE checks the method result and sees the failure but it doesn’t record the error. It’s possible that the error is being logged by the underlying code. Do you see any correlated log entries with a subsystem of com.apple.cipherml. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880228022, WangZiYuan, /thread/817264?answerId=880228022#880228022, /profile/WangZiYuan'] I do receive the startFilter and stopFilter messages, but I no longer receive the handleNewFlow message [/quote] Well, presumably you receive the stop call before the start call (-: But that still doesn’t answer the question I posed upthread, and the answer to that question is critical in determining how to continue investigating this issue. When you disable and the re-enable the filter, you receive a stop and then a start call. Does the process ID change between the two? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880167022, parker9, /thread/810258?answerId=880167022#880167022, /profile/parker9'] GitHub has the actual source for that version in Releases [/quote] OK. I downloaded the app, the .dSYM, and the source code and took a look. First, the crash report has this: Binary Images: 0x102c6c000 - 0x102c9ffff DIM arm64 <3e247524da7930099f63cd12ace4ab0e> …/DIM I used dwarfdump to confirm that I have the right .dSYM: % dwarfdump --uuid DIM.app/Contents/MacOS/DIM UUID: 7A4DAC69-55A2-3D1B-B9E0-6A14AB2D5EEA (x86_64) DIM.app/Contents/MacOS/DIM UUID: 3E247524-DA79-3009-9F63-CD12ACE4AB0E (arm64) DIM.app/Contents/MacOS/DIM I then symbolicated those frames: % atos -l 0x102c6c000 -o DIM.app.dSYM 0x102c799bc 0x102c8b4d4 closure #1 in ViewController.restore(_:) (in DIM) (ViewController.swift:207) thunk for @escaping @callee_guaranteed () -> () (in DIM) + 28 Plugging that into the backtrace, I get this: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 closure #1 in ViewControl

[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you option click on ad

[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you option click on ad

[quote='880037022, voidpulse, /thread/792453?answerId=880037022#880037022, /profile/voidpulse'] I see the bug was reported about 8 months ago [/quote] What was your bug number? Tracking down local network privacy issues is hard, and the thing that helps the most is good quality bug reports. For an example of that, see this thread, resulting in FB21858319. The issue described in that thread is a generic one. While the developer who filed the bug did so with very specific steps-to-reproduce, the bug itself is timing dependent and thus can crop up in a wide variety of scenarios. So, it’s possible that this fix will help in your case as well. However, the fix isn’t currently being seeded, so you can’t currently tell whether that’s the case or not )-: I recommend that you monitor that other thread for updates. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880105022, hasii2021, /thread/818406?answerId=880105022#880105022, /profile/hasii2021'] I will continue to monitor this [/quote] Please update this thread if you learn more. I try to keep track of all the weird code signing errors and what causes them — one day I’ll write a technote based on that — and I’m super curious how you’re hitting this. Oh, actually, come to think of it, you can reproduce this, so it’d be worth filing a bug about it. So, if you have the time and inclination: Create a read/write disk image that’s big enough to hold your app. Copy the app on to it. Reproduce the error. And then immediately trigger a log snapshot: % sudo log collect --last 5m Adjust the --last parameter to a bigger value if code signing takes a really log time (-: And then a sysdiagnose log. Unmount the disk image. File a bug with that disk and the logs from steps 4 and 5. Once you’re done, reply here with the bug number and I’ll see what I can uncover. But I do understand if you’re not able to do this; you have

[quote='880086022, smjkrk, /thread/814261?answerId=880086022#880086022, /profile/smjkrk'] we still get this issue with iOS 26.3 and 26.3.1. [/quote] Bummer. At this point I think I’m gonna double down on my earlier suggestion to file a bug about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Earlier I wrote: [quote='880097022, DTS Engineer, /thread/818192?answerId=880097022#880097022'] the … question is really about whether your app extension can call StoreKit [/quote] I’ve confirmed that we don’t support StoreKit in app extensions [1]. At this point I don’t see a good solution. You can certainly file an enhancement request explaining your use case and requesting that we support it, but that won’t help in the short term. Note If you do file an ER, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Apparently there’s an exception for iMessage extensions, but that doesn’t help you.

Thanks for the clarification. I kicked off some research about this but I probably won’t have any updates soon. I hope to have more info around the end of next week. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The outage described in this thread was resolved on the same day that it occurred. If you’re working in an Enterprise team and having problems deploying your apps, I recommend that you seek help from either your MDM vendor or, if you’re doing this yourself, from Apple Support. You can also see community help over in the Apple Support Community, and specifically in the Business and Education topic area, where you’re more likely to find folks with enterprise app deployment experience. I’m locking this thread because a) the issue it covered is most definitely resolved, and b) I don’t want it to become a distraction for folks who have enterprise deployment problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There is no approval process for creating an NE packet tunnel provider [1]. Any paid developer can do that [2]. Why do you think that such an approval is necessary? If you’re using Xcode, you should be able to add the Network Extension capability to your app and appex, check the Packet Tunnel box, and let its automatic code signing handle the rest. But you’re the second person to ask a question like this recently [3], suggesting that something is misleading folks. I’d like to find that and fix it. ps Some NE providers have deployment restrictions. See TN3134 Network Extension provider deployment for the details. Also, don’t try to use a packet tunnel provider for something other than VPN. See TN3120 Expected use cases for Network Extension packet tunnel providers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Other than approval to join the Apple Developer Program itself. [2] That wasn’t always the case. See Network E