“eskimo”

[quote='844482021, thespian, /thread/844482, /profile/thespian'] Is it supported to consume packets … send them to the public Internet without a remote VPN endpoint [/quote] No. Packet tunnel providers are intended to be used for VPN and, by definition, that involves a VPN server. While it may be possible to do what you’re trying to do [1], DTS doesn’t support that. See TN3120 Expected use cases for Network Extension packet tunnel providers. Note This is a DTS policy. I don’t work for App Review and can’t comment on their policies. I suspect you’re on iOS, in which case your alternative options are limited. If you happen to be targeting macOS, you can do this sort of thing using a transparent proxy. TN3134 Network Extension provider deployment has more info about the distribution limitations for the various NE provider types. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I’ve seen deeply approaches used: Re-inject pac

[quote='903834022, KrishnaveniNalka, /thread/844416?answerId=903834022#903834022, /profile/KrishnaveniNalka'] Created FB24619068 [/quote] Thanks. That’s the best path for this. It’s generally true that your app should be able to trigger a system-wide hang! Looking at your bug I see there’s no sysdiagnose log. Please take one at the time of the hang and then add it to your bug. Even though you’re attached a test project — and thanks for that! — a sysdiagnose log is important to make sure your bug gets routed correctly. See our Bug Reporting > Profiles and Logs page for more about sysdiagnose logs. Oh, and if the standard key chord doesn’t work when the system is hung like this, you can SSH into the Mac and run the sysdiagnose command-line tool. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The behaviour you’ve described doesn’t surprise me. I’ve not looked into the Ethernet side of this, but what you’re seeing closely matches the Wi-Fi behaviour. That is: If you lock the screen, your app moves to the background and shortly thereafter gets suspended, meaning that it’s unable to perform networking. If the device sleeps, the system disassociates from Wi-Fi. I talk about these ideas in a lot more detail in the various posts linked to from Extra-ordinary Networking. [quote='903945022, Qinhan_Li, /thread/844516?answerId=903945022#903945022, /profile/Qinhan_Li'] Does this require MFi support … ? [/quote] AFAIK MFi doesn’t have any specific provisions for Ethernet. [quote='903945022, Qinhan_Li, /thread/844516?answerId=903945022#903945022, /profile/Qinhan_Li'] Does this … a specific iOS entitlement? [/quote] AFAIK there are no entitlements related to this. What’s the actual problem you’re trying to solve here? I suspect that you’re trying to communicate between your app and this Ethernet-based accessory

The iOS SDK has no APIs for getting precise CPU core temperatures. If your goal is to adjust your app’s behaviour based on the thermal state, there are APIs to help with that. The general-purpose API is ProcessInfo.thermalState (see here), but there may be more specific APIs provided by the subsystem you’re working with. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

While it’s true that we don’t support third-party tools in general, in this case I think you’ll find that the same issue affects Xcode-built apps. And, yeah, these URL schemes are something you’ll have to test on real hardware. The simulator is a great tool for day-to-day development, but it’s a simulator, not an emulator, and thus a lot of integration-y stuff just don’t work there. Oh, and btw, error -10814 is actually a public error code in the macOS SDK, namely kLSApplicationNotFoundErr. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='903727022, twardakm2, /thread/844177?answerId=903727022#903727022, /profile/twardakm2'] In our case we use it to block specific DNS from being resolved. [/quote] And your packet tunnel provider is doing that because? [quote='903727022, twardakm2, /thread/844177?answerId=903727022#903727022, /profile/twardakm2'] I reported Feedback to using Feedback Asistant: FB24536764. [/quote] Fair enough. I took a quick look and this has been dup’d to a bug filed by a different developer in a similar situation. It’s possible that the NE team might address this. However, to reiterate, DTS doesn’t support this technique. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FB24609180 Thanks. Oh, and a quick look at that bug suggests that it might be worth checking again on iOS 27 beta, because 27.0b5 and later have improvements in this space. (I’d do it myself but I’m super busy right now.) But for now I'll proceed under that assumption and see how far I get. Cool. Also, are you getting crash reports from Xcode organiser? If you are, those should confirm my theory. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks. I’ll be in touch via your DTS case. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, there are now three different folks on this thread. That makes it hard to respond to any one of your specifically, so I’m going to post a generic reply. If the test that I described earlier reveals a problem, my advice is: File a bug describing the overall issue you’re hitting and the specific test your ran, and then attach the .ipa that you generated as part of that test. Post the bug number here, just for the record. Contact Apple > Developer > Contact Us and ask them to rename you team to remove the non-ASCII characters, being sure to reference the bug from step 1 as justification. Sadly, this is not the only situation where ‘weird’ character cause problems for code signing: This thread describes an issue where double quotes in the team name cause similar issues. This reply explains how a non-ASCII character in the name of a file within the bundle can cause problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + appl

OK, you posted two replies that touch on two separate issues. I want to address the first issue first, then we can come back to your installer package issue. Oh, before we do that, if you need to post a Terminal transcript, it’s best to do that as text in a code block rather than as a screenshot. That makes it much easier to read, and also allows me to copy’n’paste. See tip 5 in Quinn’s Top Ten DevForums Tips for more about this. [quote='903706022, Thededicated, /thread/843122?answerId=903706022#903706022, /profile/Thededicated'] The notarization fails and the status displays : Invalid [/quote] OK. Then the next step is to fetch the notary log and see what it’s complaining about. See Fetching the Notary Log for info on how to do that. If you’d like my input on that log, feel free to post it here. You can post it either as a text attachment [1] or, if it’s relatively short, in a code block. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 +

[quote='903748022, asmedley, /thread/840500?answerId=903748022#903748022, /profile/asmedley'] Added FB24608345 with some diagnostics [/quote] Hey hey, that was just what I was about to ask for (-: Just to be clear, the sysdiagnose log you attached is from the guest, right? Because in this case that’s what we need. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='844378021, starmike, /thread/844378, /profile/starmike'] is this a valid reason for granting me com.apple.vm.device-access? [/quote] com.apple.vm.device-access is intended for virtualisation apps that ship on the Mac App Store. Is that what you’re building? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I suspect that you were only granted this capability for development. You can check that for yourself using the process described in Finding a Capability’s Distribution Restrictions. [quote='844352021, SurrealityLab, /thread/844352, /profile/SurrealityLab'] When we use “Automatically manage signing” our app properly builds and deploys to the Vision Pro [/quote] Right. That’s because automatic code signing uses development signing identities and profiles, and the capability is available to you in that case. [quote='844352021, SurrealityLab, /thread/844352, /profile/SurrealityLab'] but when we use the app and attempt to access the main camera, the app crashes with the exception [/quote] That’s probably a different issue. If you still had provisioning problems, you app wouldn’t build or run. The fact that it builds and runs indicates that your entitlements are all good. But let’s run a test, just to confirm that: In Xcode, build and run your app on the device. Still in Xcode, choose Product > Show Build Folde

[quote='844239021, Ere0n, /thread/844239, /profile/Ere0n'] both the SecureGuard host app and its ES system extension run under Rosetta translation. [/quote] What? While I’m not surprised that this works — Rosetta is really good at what it does — it’s not something that we [1] are going to support. That’s because: Rosetta is going away. Indeed, Apple reconfirmed the timeline for that just yesterday. ES clients are performance critical, and relying on Rosetta runs counter to that requirement. I think it’s very unlikely that this combination has ever been tested. It’s not necessary for “backward‑compatibility with older Intel‑based Mac hardware”. Standard practice here is to ship a universal binary, where Intel-based Macs run the Intel slice and Apple silicon Macs run the ARM one [2]. See the various docs under Apple silicon IMO you should fix this first, and then get back us if you continue to have problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

[quote='844341021, svleest, /thread/844341, /profile/svleest'] 1- Is a prefix update the correct and available fix here? [/quote] Yes. There are a couple of caveats I want to highlight: Keychain access — Fortunately it doesn’t look like this is an issue for you. For anyone else reading along at home, I talk about this in depth in App ID Prefix Change and Keychain Access. Extensions — If your app contains any extensions, make sure that you’re clear with DevPrograms that they need to change the prefix on those App IDs as well. [quote='844341021, svleest, /thread/844341, /profile/svleest'] 2- Is there any developer-side workaround … ? [/quote] No. [quote='844341021, svleest, /thread/844341, /profile/svleest'] 3- Any way to escalate the support case … ? [/quote] No. The case number you posted indicates that you’re in touch with DevPrograms, who are the right folks to deal with this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.c