Apple Maps Guides

[quote='861351022, oddeyed, /thread/799110?answerId=861351022#861351022, /profile/oddeyed'] Yes, that is correct. [/quote] OK. That certainly does raise a world of possibilities. The approach I usually recommend for incremental Apple installers is to copy the app and then update the copy. See this post. However, I don’t think that’s feasible for an installer package, and I’m not 100% sure what the best option here is. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='861284022, dylandylandylan, /thread/757444?answerId=861284022#861284022, /profile/dylandylandylan'] Is there any way that startVPNTunnel() can fail, without an error being thrown? [/quote] Well, I think you’ve answered your own question there (-: Obviously this shouldn’t happen. A successful call to startVPNTunnel(…) isn’t guaranteed to bring up the tunnel, but it should at least get it into the .connecting state. If that’s not happening, I think it’d be reasonable to file a bug about it. Please post your bug number, just for the record. Your bug will need a sysdiagnose log taken after seeing the problem. Ideally this sysdiagnose log would be: Taken on a device with the VPN (Network Extension) debug profile installed; see our Bug Reporting > Profiles and Logs page for more on that. Taken immediately after seeing the problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m going to close out this thread. Lemme explain my rationale… The primary issue being discussed here is installing a root certificate without explicit approval from the user such that it’s trusted system wide. There are two different cases: Doing this programmatically Doing this from Terminal or from a shell script For the programmatic case, there’s no supported solution. This isn’t a bug but a deliberate security hardening, as I explained in this post. For the Terminal and shell script case, DevForums isn’t the right place to have that discussion because: Our focus here is primarily on APIs, not device management. Many of the workarounds suggested on this thread rely on implementation details, which is counter to the forums’ focus on APIs. If you want to continue exploring device management options, I encourage you to pop over to the Apple Support Community, run by Apple Support, and specifically the Business and Education topic area. Finally, there’s one very clear path forward here: Ins

[quote='803114021, trustdben, /thread/803114, /profile/trustdben'] until the device is rebooted. [/quote] I recommend that you file a bug about this. Things that need a restart to clear are almost always a bug in one layer on the system or another. Please post your bug number, just for the record. For your bug to get traction it’ll need to have a sysdiagnose log attached, one that was taken on the affected device after you see the problem. I realise that this might be hard to get due to the intermittent nature of the bug. I have some hints and tips about this in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Ideally this sysdiagnose log would be: Taken on a device with both the Network Diagnostics and VPN (Network Extension) debug profile installed; see our Bug Reporting > Profiles and Logs page for more on that. Taken immediately after seeing the problem. That’s hard if you’re investigating this based on reporting coming in from the field, but keep that in mind if you’re making a concerted

The thread referenced by RickMaddy has a lot of backstory here, but I want to address this bit specifically: [quote='803112021, sincos2007, /thread/803112, /profile/sincos2007'] does xcode in guest work? [/quote] Xcode does work in the guest but with one significant limitation: You can’t run Mac apps that use restricted entitlements [1]. For some folks that’s a complete showstopper. For others it’s a non-issue. If this a problem for you, I recommend that you watch the above-mentioned thread where I’ve been posting updates about new developments in this space. Oh, and all of the above is assuming you’re on Apple silicon. The story for Intel-based Macs is very different. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Those that must be authorised by a provisioning profile. See TN3125 Inside Code Signing: Provisioning Profiles.

[quote='803127021, development, /thread/803127, /profile/development'] Added the NSAppTransportSecurity key to the Info.plist file [/quote] Just FYI, ATS only applies to high-level APIs, so URLSession and things layered on top of it. It’s irrelevant to folks using lower-level APIs, like Network framework and BSD Sockets. Still, it doesn’t hurt to turn it off temporarily during testing (-: [quote='803127021, development, /thread/803127, /profile/development'] These are the prints made during the procedure. [/quote] My best guess here is that the remote peer is closing the connection immediately on receiving the Client Hello message. I’ve seen problems like that in the past, where a TLS implementation sees a newer version of the protocol, or a new TLS extension, and fails to handle it properly [1]. I recommend that you use a use a packet trace to see what’s happening on the ‘wire’. If my theory is connect, you’ll see: The SYN / SYN-ACK / ACK handshake, setting up the TCP connection. The TLS ClientHello coming f

Hi there — I saw your post about the Retention Messaging API. I’m in the same situation: we submitted an access request a while ago but haven’t heard back from Apple yet. Did you eventually get any response or approval from them? Thanks in advance for sharing your experience!

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

For help with connecting displays, please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers.

Glad to hear it re: upgrading to Xcode 26.1. As for discrepancy between shipping API and docs that's problematic and we'd appreciate help in identifying these areas. A performance tuning guide sounds helpful. bfloat type support likewise compelling for machine learning. We'd appreciate any feedback you could provide for documentation in an enhancement request.

Thanks for getting back to me! It appears that upgrading to Xcode 26.1 has fixed the issue, and the headers are now detected correctly. By the way, I noticed that there is a lot of discrepancy between the documentation and the shipped APIs. I suppose you guys are aware of this and working on a fix? And we really need a Performance Primitives tuning guide. The API is very flexible and finding settings that actually work well for performance can be challenging. For example, I am yet to find a tile size for which using a multi-simdgroup execution scope would not result in performance regression. Also, what about bfloat?