“Apple Maps Guides”

I’ve been discussing your issue with the vmnet folks and I think I have a handle on what’s going on here. However, I want to run some things past you before I say anything definitive. Consider this setup: ---+--------+--------- Wi-Fi to Internet | | host Mac X | ---+---+-------------- vmnet | guest VM My understanding is that software running on the host Mac is unable to connect to a server running on the VM via the public port (8000), even though you have forwarding configured in vmnet. Have you tried doing the same from some other machine on the host’s network, so X in this case? Well, using the host Mac’s Wi-Fi IP address, obviously, not using localhost (-: Also, you wrote: [quote='884688022, rbmanian75, /thread/822658?answerId=884688022#884688022, /profile/rbmanian75'] But i found that reaching http://guestip:port worked fine. [/quote] Is that when only using the API? Or with pfctl hackery? If it’s the latter, I’d appreciate you concentrating on the former, because that’s the only thing we support [1]. As

And that’s why it’s good when folks post their bug numbers (-: Looking up the status of FB21130604 I see that we actually passed a workaround on to the originator. And one of my colleagues also sent them the workaround via an issue filed against their test project. See here. Nice! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884571022, idopte, /thread/822656?answerId=884571022#884571022, /profile/idopte'] My main concern is that … [/quote] I’m not sure what I can do to alleviate that concern here on the forums. Given that you have a working system but you’re concerned that the documentation is not sufficiently clear to determine whether that’s correct, I think your best option is to file a bug for better documentation. 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='884572022, kpatel1991, /thread/821961?answerId=884572022#884572022, /profile/kpatel1991'] the ShareableCredential one appears but even if we check it - Xcode still isn't allowing us to deploy. [/quote] Right. That is the nature of the bug in question here (FB22439399). You need to apply for the Contactless Pass Provisioning (deprecated) capability. There’s no form to do that specifically, so use the common Contactless Pass Provisioning capability form. [quote='884560022, Nagavendra, /thread/821961?answerId=884560022#884560022, /profile/Nagavendra'] It’s working now with the following approach … [/quote] Excellent news. [quote='884560022, Nagavendra, /thread/821961?answerId=884560022#884560022, /profile/Nagavendra'] However, this does not seem like a proper or permanent solution. [/quote] Indeed. The permanent solution will involve a fix to Xcode, which is what we’re tracking with the above-mentioned bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail =

[quote='822908021, unni0786, /thread/822908, /profile/unni0786'] Is com.apple.managed-keychain the correct entitlement for this use case? [/quote] I don’t think so. I’ve never even heard of that before, and there’s certainly no documented way to apply for it. [quote='822908021, unni0786, /thread/822908, /profile/unni0786'] the cert profile configured as always available in MDM. [/quote] Again, that’s not something I’m aware of. It’s possible that you’re talking about the AllowAllAppsAccess property, as documented here. If so, that’s a Mac-only thing. In general, iOS apps cannot access credentials installed via MDM configuration profiles [1]. Historically, folks with this general requirement didn’t have a good path forward. These days we have an excellent new option, the ManagedApp framework. It’s super cool. For a short intro, watch WWDC 2025 Session 203 Get to know the ManagedApp Framework. However, I don’t think it’ll help you, because your app is specifically concerned with the state of credentials there w

Let’s focus this discussion on your earlier thread. If you have new information, feel free to post it by replying on that thread. And, yes, I realise that no one has responded to you over there. I’ve been hoping to get to it but I just don’t have time right now )-: However, starting a second thread isn’t helping anyone. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

In the Apple world there is no such thing as a “GUI-less application”. Apps are user-visible things that you launch from the Finder, the Home screen on iOS, and so so. If you’re building an product that relies on a system extension (sysex) then my general advice is: Embed the system extension in a container app that has a GUI that allows the user to install and remote the sysex using System Extensions framework. And, in the case of a NE provide, configure it using the Network Extension API. If you need some other background processing functionality — like a launchd daemon or agent — embed that in your app and manage it via SMAppService. If you want to support customers in a managed environment, explore the various MDM options for installing your app, enabling your sysex, and configure its options. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='823069021, natasha_m, /thread/823069, /profile/natasha_m'] What is the effective validity period of an Ad Hoc build? [/quote] My understanding is that: This is gated by the app’s provisioning profile. Ad Hoc provisioning profiles live for about a year. However, you can check this for yourself by dumping the provisioning profile. TN3125 Inside Code Signing: Provisioning Profiles explains how to do that. IMPORTANT Some types of provisioning profiles have an ExpirationDate property, which makes the expiration date very clear. In others you have to combine the CreationDate property and the TimeToLive property, the latter being a count of days. Development provisioning profiles have a similar limit, and you can work that out in the same way. [quote='823069021, natasha_m, /thread/823069, /profile/natasha_m'] If we distribute the app using a development (debug) build via provisioning profiles, what is the expiration timeline? [/quote] You need to distinguish between: Build configuration (Debug or Release) Co

Albert’s provided some good info, but I want to talk about the big picture here. Why are you asking about this? From an API perspective, ~/.CFUserTextEncoding is an implementation detail. If you’re writing code, the location, format, and function of that file shouldn’t matter. Can you elaborate on the context which caused you to ask this question? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com