“eskimo”

[quote='878127022, Pelea, /thread/817433?answerId=878127022#878127022, /profile/Pelea'] Yes, I already tested that method. [/quote] Cool. [quote='878127022, Pelea, /thread/817433?answerId=878127022#878127022, /profile/Pelea'] But unfortunately, [they] don’t include the Handshake payload [/quote] Bummer. I actually chatted with the Network framework team about this overnight and they think that it should work the way you want it to work. Given that, my advice is that you file a bug against the data transfer report feature. 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

[quote='878132022, miekari, /thread/817442?answerId=878132022#878132022, /profile/miekari'] making it unavailable for consumer App Store distribution [/quote] Indeed. These restriction are not accidental, and if you try to use a packet tunnel provider to get around them then you are going to run into problems. [quote='878132022, miekari, /thread/817442?answerId=878132022#878132022, /profile/miekari'] Is there a supported way to deliver DNS responses larger than 512 bytes through NEPacketTunnelFlow? [/quote] Packet tunnel providers work at the IP layer, which means you can’t just deliver a large UDP datagram to the system and expect it to work. You will have to fragment the datagram, just like the TCP/IP stack would. There’s no API for this; you’ll have to write your own code. If you continue down this path, I recommend that you prototype it using a client that you control. That is, create a small test app that issues a UDP DNS request that triggers a large response and then tries to read that response. That w

[quote='878157022, JonathanBley, /thread/817353?answerId=878157022#878157022, /profile/JonathanBley'] does this mean there is no possibility … ? [/quote] It’s hard to prove a negative |-: I’m working from published process, just like you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='878252022, someonelikeme, /thread/817520?answerId=878252022#878252022, /profile/someonelikeme'] I'm not sure I could make something out of those sysdiagnose logs [/quote] Ah, you’ve not met spindumps before! A spindump includes a backtrace of every thread in every process on the device, making it perfect to debug problems like this. If you unpack a sysdiagnose log, you’ll see the spindump in a file called spindump-nosymbols.txt. When dealing with issue like this, I find it useful to force the problem to happen — like add a sleep call to your main thread — and then do the diagnostic that you’re asking the user to do. You can then take the resulting sysdiagnose and confirm that you’re able to get from the spindump to your sleep call. That way you can be sure that the diagnostic you’re asking the user to create is actionable. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='817620021, dukebuilder, /thread/817620, /profile/dukebuilder'] does the form need to be submitted once per Bundle ID [/quote] Yes. Well, once for the app and again for all the app extensions that use the Family Controls capability. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m having trouble reading that log. Can you post another copy, this time formatting it as a code block? If you’re not familiar with the code block format, there’s advice on that in tip 5 of Quinn’s Top Ten DevForums Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='817602021, Pavel, /thread/817602, /profile/Pavel'] On macOS, the socket path length is restricted to 104 characters [/quote] That’s not quite right. While sockaddr_un has a fairly short limit, a Unix domain socket address actually supports a path length up to 253 bytes, which is SOCK_MAXADDRLEN minus the two byte header containing sun_family and sun_len. However, sockaddr_un is defined such that sun_path is 104. So, if you’re happy to do some gnarly pointer play, you can use longer paths, long enough to allow them to live within an app group container. Oh, wait, you said not sandboxed. Well, in that case, you don’t need to put them in an app group container, but you can still take advantage of the long path support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='878228022, DTS Engineer, /thread/815285?answerId=878228022#878228022'] So, my own, entirely personal and slightly radical, perspective [/quote] I so agree with this! I can’t remember if Kevin radicalised me, or I radicalised Kevin, or perhaps we were both radicalised by the File Manager APIs that Apple introduced in Mac OS 9 (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

VictorPetitjean and friends asked me about the state of FB21858319 via some other channel, and I thought I’d share what I can here for the benefit of all. In short, the fix for FB21858319 is not in the current 26.4 beta seed. Sadly, I can’t predict the future, so I can’t say anything definitive as to whether this fix will catch the 26.4 train at all. Normally I’d end a response like this with “I recommend that you continue testing as new beta seeds become available.” In this case, however, this is a hard-to-reproduce problem, and thus I can understand why you might want to hold off on that until you’re notified of the fix being in a specific beta seed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877954022, pawanquantum, /thread/817434?answerId=877954022#877954022, /profile/pawanquantum'] The sample code I shared reproduces this exact state — it's a loopback tunnel that never forwards packets. [/quote] Sure, but that’s not how packet tunnel providers products usually work. In most cases the provider won’t bring up the tunnel, by calling setTunnelNetworkSettings(…), until it’s ready to actually forward packets. You have a couple of choices here: You can file a bug requesting that we change iOS to make this work. You can change your packet tunnel provider so that it works in the standard way. Or you could do both (-: If you do file a bug: Make sure that your bug report explains why you packet tunnel provider has to bring up the tunnel before it’s ready to forward packets. Without that, your bug is likely to get bounced back saying ‘stop doing that’. Enable additional NE debugging on your test device, via the VPN (Network Extension) for iOS/iPadOS profile on our Bug Reporting > Profiles and Lo

[quote='878094022, WangZiYuan, /thread/817264?answerId=878094022#878094022, /profile/WangZiYuan'] I’m not quite sure what you mean by the 'sysex process.' [/quote] OK, lemme clarify. On macOS, content filters must be packaged as a system extension [1], aka a sysex. A sysex is much like a launchd daemon, in that it can potentially run for the entire boot cycle, that is, start when you boot the Mac and not stop until you shut down [2]. Your Network Extension provider instances are created within that sysex process. So, consider this sequence: You boot your Mac. Your sysex starts. NE instantiates your content file provider within that sysex process. You stop the filter. NE stops the content filter provider. At this point the system may or may not stop your sysex process. But let’s consider what happens if it doesn’t… You start the filter again. NE instantiates your content file provider again, still within the same sysex process. So, my questions are: Are you seeing the sysex process stop at step 6? If not, if y

[quote='878015022, KayleeSC, /thread/791352?answerId=878015022#878015022, /profile/KayleeSC'] Of course the new beta would break the whole thing immediately [/quote] So lemme see if I understand this problem: Your app on TestFlight works on iOS 26.3. But fails with that error an iOS 26.4b3. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877970022, MatteoMonizza, /thread/805681?answerId=877970022#877970022, /profile/MatteoMonizza'] Yes, I'm able to reproduce this every time. [/quote] Oh, that’s interesting. Other folks haven’t been able to reproduce this, so the fact that you can could really help with the investigation. Are you able to cut down your app into a minimal test project that still reproduces the problem? Alternatively, do you have an app that’s currently in the store that can reproduce the problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877933022, bbtyou, /thread/792744?answerId=877933022#877933022, /profile/bbtyou'] This bug still exists in iOS 26.2.1 [/quote] It’s possible that you’re seeing a different aspect of it than blacksun. Given that, my advice is: Retest on iOS 26.3 and the current 26.4 beta, just to make sure that you still see the problematic behaviour. If so, file your own bug about it. 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

AFAIK this situation hasn’t changed since my last reply here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com