eskimo

[quote='813735021, Catonian, /thread/813735, /profile/Catonian'] with Always-On / On-Demand VPN [/quote] To be clear, Always-on VPN is a very specific thing that’s not supported with third-party VPN products (r. 21363342) [1]. My experience, based on the number of problems I’ve seen here on the forums, is that folks who try to use VPN On Demand to simulate Always-on VPN are invariably disappointed )-: Given that, I’m not sure how much I can help you here. My general advice: If you would like to track the state of the above-mentioned enhancement request, file your own ER and ask that it be dup’d to problem 21363342. If you’re able to reproduce the problem you’ve described on macOS 26, you should consider filing a bug about that. And there’s nothing stopping you from doing both (-: If you do file a bug for the problem you’re seeing: Make sure you can reproduce it on macOS 26. You mentioned that you’re seeing this on macOS 14 and 15, and there’s probably not much point filing a bug against those systems. Attach

Thanks for the post. Wow trying to go down the memory lane on iOS 14 and 15. If think you've diagnosed the problem perfectly. In my opinion, your issue is almost certainly because the com.apple.developer.carplay-driving-task entitlement is only available for iOS 16 and later as you said. To make your app compatible with iOS 14 and 15, you must fit into one of the legacy categories and obtain the corresponding entitlement from Apple. If your app has any audio playback features, applying for carplay-audio is the most common and straightforward path. If your app is for navigation, you’d apply for carplay-navigation. I would recommend to go to the Apple Developer website and request the appropriate CarPlay entitlement. https://developer.apple.com/contact/carplay/ Fill out the form, specifying the App ID and the entitlement you are requesting (e.g., carplay-audio). Follow this documentation https://developer.apple.com/documentation/carplay/requesting-carplay-entitlements I could be wrong so please do follow the do

I need to clarify a bunch of things, but before I do that I want to point you at Quinn’s Top Ten DevForums Tips, and specifically: Tip 5 — This explains how to format your post to make it easier to read. Tip 7 — This helps head off follow-up questions (like the ones below). So, my questions: This is macOS, right? Is this a regression? Or are you seeing this problem on a wide range of macOS versions? Have you tried it on the most recent macOS 26.3 beta seed? How reproducible is this? Once it occurs, how long does it persist? Does it go away if the provider exits? Or if you start and stop it? Or if you restart the machine? If this is a regression, have you file a bug about it already? If so, what was the bug number? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the updated posts. [quote='873386022, Leo_Nagano, /thread/812857?answerId=873386022#873386022, /profile/Leo_Nagano'] legacy dns-proxy entitlement [value] [/quote] To be clear, this isn’t a legacy value. This value is used for App Store distribution, both on iOS and macOS. It’s also used for development. The -systemextension suffix is used for direct distribution using Developer ID signing. Neither value is more legacy than the other. As to what’s going wrong, you’ve tried a lot of different things and it’s hard to be sure what’s what at this state. However, this is problematic: NSExtensionPointIdentifier com.apple.system_extension.network_extension And it suggests that you could do with some high-level guidance. The best place to get that is Xcode. Consider this sequence: In Xcode 26.2, create a new project from macOS > App template. In my case I named it “Test812857”. Then create a new target within that project, using the macOS > System Extension > Network Extension template. In my case

[quote='873484022, oddeyed, /thread/799110?answerId=873484022#873484022, /profile/oddeyed'] My application currently requires elevated privileges or “sudo” to verify the codesign … [/quote] Lemme see if I understand this correctly: You take a Mac that’s never seen your app before. You install your app in the standard way that a user would install it. This command fails: % codesign --verify --deep --strict /path/to/your.app Instead you have to do this: % sudo codesign --verify --deep --strict /path/to/your.app Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873483022, lilan, /thread/773414?answerId=873483022#873483022, /profile/lilan'] Sorry if it's really basic. [/quote] This is definitely not basic. Getting all of these ducks to line up is a significant challenge. My point is that there are lots of resources to help you. [quote='873483022, lilan, /thread/773414?answerId=873483022#873483022, /profile/lilan'] But I really don't know where to start. [/quote] I suggest you start with the documentation for the PIR Service Example package: Go to the page I linked to above. At the top right you’ll see a link to the documentation on the Swift Package Index. Click that. Explore that documentation. [quote='873483022, lilan, /thread/773414?answerId=873483022#873483022, /profile/lilan'] can we run it on xcode … ? [/quote] Quoting the read me for that package: macOS or Linux operating system Swift version 6.0 or later Optionally, XCode version 16.1 or later [quote='873483022, lilan, /thread/773414?answerId=873483022#873483022, /profile/lilan'] can we … connect to o

It’s hard to tell from this side of the fence, so let’s tag in @linkerkitkat . Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873385022, Eligian, /thread/813441?answerId=873385022#873385022, /profile/Eligian'] This is … account level … [/quote] Right. My experience, based on what I see here on the forums, is that: Once you enter this state, it affects all notarisation for that team until the state clears. This state usually clears after a day or two. If you remain stuck after a week, please post: The request UUID of the oldest stuck request The creation date of that request and I’ll dig deeper. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873489022, roanutil, /thread/811382?answerId=873489022#873489022, /profile/roanutil'] can the app target be left using the old team id? [/quote] I believe so. My best guess is that this is a deliberate choice on our part, so that app transfers don’t result in users losing all their iCloud key-value store preferences (in contrast to, for example, keychain items [1]). However, I’ve never seen the exact behaviour documented anywhere. I’m going to research this further and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See App ID Prefix Change and Keychain Access.

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. 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s hard to offer insight here without a full Apple crash report. Does anyone have one of those? If so, please post it here. See Posting a Crash Report for advice on how to do that. [quote='870052022, brianindeed, /thread/810678?answerId=870052022#870052022, /profile/brianindeed'] Do these [iOS] versions correspond to the RC or the GM? [/quote] You can tell that from the format of the build numbers. For example, in 23C5027f you have: 23 — This maps to the major version number, in this case iOS 26. C — This maps to the minor version number [1], making it iOS 26.2. 50 — This contains the build number prefix; see below for more on that. 27 — This is the actual build number. f — This is something internal that I’m not going to go in to. In seed builds we prefix the build number with a digit indicating the type of build, padding it up to three digits with leading zeroes. So 5027 is build 27 with a build type of 5 [2]. In released builds we don’t do this padding. For example, the release build of iOS 26.2 running

I’m not aware of any official documentation about time.apple.com. Given that, you have to treat it like an implementation detail. It sounds like your app really needs trusted timestamps. That is, if the time service went away, your app would cease to function properly. Given that, I recommend that you use a time service that’s documented to be appropriate for your use case, or something that you run yourself. 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

[quote='873465022, Eligian, /thread/811968?answerId=873465022#873465022, /profile/Eligian'] Did this ever get resolved? [/quote] This is case specific, so there isn’t a “this” to get resolved. Rather, the resolution of each case is separate, and possibly different. We’re already discussing your case over on your thread, and I’ll reply over there shortly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com