Apple Maps Guides

Thanks again for reporting the issue. It seems that the issue is impacting the community, but I haven't seen any feedback report ID posted here. Do folks have any feedback report yet? If not, would you mind to file one and share your report ID here? I understand that filing an actionable feedback report takes time, but that will help. I am trying to capture the issue, and yet, my current configuration, Xcode 26.2 (17C52) + iPhone 17 Pro with iOS 26.3 (23D127) + Apple Watch series 10 with watchOS 26.3 (23S620), does work for me. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Nope, no updates. We made several more requests to Apple Support - no answers.

[quote='854085022, DTS Engineer, /thread/797007?answerId=854085022#854085022'] Keep in mind that appex-based VPN isn’t well aligned with macOS’s execution model. macOS supports multiple users simultaneously, which is a concern because VPN configurations affect the networking stack as a whole. [/quote] So how does that explain network app extensions in App Store apps? What is there to stop a user logged in on the same system (possibly a standard user) from accessing a VPN tunnel started by another higher privileged user via a Mac App Store app with a network app extension and gaining unauthorized access to resources via that tunnel? I would think most people assume App Store apps to be running in a far more restricted environment than apps distributed outside the App Store, but in the case of app extensions the opposite appears to be the case. By forcing Developer ID apps to use system extensions it forces admin privileges in order to install the extension and the explicit granting of Privacy and Security perm

[quote='876733022, disinghal, /thread/811887?answerId=876733022#876733022, /profile/disinghal'] URL Session is calling a public endpoint. [/quote] Right, but you’ve set up your on-demand rules to say that everything generates demand. It’d be interesting to see what happens if you configure your on-demand rules to only generate demand what you load a URL that’s behind the VPN. I suspect it’ll work consistently, but if you find that’s not the case then that’d be an interesting datapoint. [quote='876733022, disinghal, /thread/811887?answerId=876733022#876733022, /profile/disinghal'] It happens intermittently. [/quote] Fair enough. But that doesn’t really contradict the position I explained above. You’ve set yourself up for failure and that you only fail in some cases. That’s a win, right? (-: Seriously though, I don’t think I’m going to be able to help you further here. You are clearly exploring the limits of what’s possible. If you want to make the case that this should work, I recommend that you do that direct

This is not a very difficult API to use: let url: URL = … let verdict = await NEURLFilter.verdict(for: url) switch verdict { case .unknown: … you need to decide on a policy for this case … case .allow: … continue loading the URL … case .deny: … stop loading the URL … @unknown default: … you need to decide on a policy for this case … } Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Issue has been solved by requesting apple developer call

[quote='876709022, siddhant-mac, /thread/815755?answerId=876709022#876709022, /profile/siddhant-mac'] is it possible on the macOS login window? [/quote] That depends on what you mean by “it”: If you’re asking whether it’s possible to reuse infrastructure used by Platform SSO then the answer is “No.” If you’re asking whether it’s possible to create an authorisation plug-in that presents a completely passwordless experience, the answer is more nuanced. You can certainly make a lot of progress, but I don’t think there’s a complete solution. Sticking points involve FileVault, as I’ve mentioned above, and unlocking the keychain. This is especially problematic when it comes to the data protection keychain. Honestly, I don’t see a good path forward for this. The authorisation plug-in mechanism has significant issues, and I’m doubtful they’ll be addressed because of limitations in that architecture. Specifically, FileVault support is pretty critical and it’s hard to see how that can happen within the current design.