Apple Maps Guides

Do you have any Apple crash reports for this? If so, please post an example. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s likely that the provisioning profile embedded in your app doesn’t authorise the new Developer ID certificate that you just created. See the Check the Signing Certificate section of Resolving Code Signing Crashes on Launch. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First up, the fact that your Developer ID signing identity is going to expire won’t affect any software that you’ve signed with it. What matters is that the certificate was valid at the time that you signed the code, and that’s ensured by a secure timestamp. TN3161 Inside Code Signing: Certificates talks about this in depth. Next, you wrote: [quote='804324021, gingerbeardman, /thread/804324, /profile/gingerbeardman'] But on the cert page it's not exactly clear to my how to renew the cert … [/quote] That’s because Developer ID signing identities are precious, and you’ve already hit the limit of the number that you can create [1]. Rather than create more, you should use one of the existing ones, ideally the one with longest remaining lifespan. To do this you’ll need to track down its private key. I talk about that in some detail in The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Actually, I co

When it was first introduced, DeviceDiscoveryUI supported a single use case, namely, a tvOS app that wants to connect to its equivalent running on a nearby iOS device. That changed in iOS 26, where DeviceDiscoveryUI is now part of the Wi-Fi Aware story. This is one of two paths into Wi-Fi Aware, the other being AccessorySetupKit. WWDC 2025 Session 228 Supercharge device connectivity with Wi-Fi Aware has the details. [quote='804414021, nikhil2701, /thread/804414, /profile/nikhil2701'] Can I use DeviceDiscoveryUI… to discover devices through Bonjour … ? [/quote] No. The DDUI support is wired up to Wi-Fi Aware’s discovery infrastructure, not to Bonjour. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

macOS 26 has a new Phone app. Did the setting land there? [1] Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Normally I’d check this for myself but I’m not set up to that right now.

Please post the full crash report, per the advice in Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Once an App ID has an associated record in App Store Connect, you can’t delete it. See Developer Account Help > Identifiers > Delete an App ID. I see two choices here: If this app hasn’t been published, create a new App ID with a completely different bundle ID part. For example, change from Com.example.WaffleVarnishPro to Com.example.waffle-varnish-pro. If it has been published, you can’t change the bundle ID part of the App ID without causing serious issues for your users, and so you’ll just have to live with the capital C. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The behaviour you’re describing doesn’t surprise me for Swift 6.0. It’s very common to find legacy completion handler-based APIs that call the completion handler on a secondary thread but don’t annotate that completion handler as sendable. We’ve taking steps to improve that in Swift 6.2, as explained in SE-0463 Import Objective-C completion handler parameters as @Sendable. There’s a couple of wrinkles here. First, you’re not actually benefiting from this because Dispatch isn’t directly imported from C, but rather has a Swift friendly wrapper. Except that it’s not really that friendly, because it doesn’t mark the execute parameter as being sendable )-: Second, lots of these problems go away when you set Default Actor Isolation to MainActor. In that case Swift will just bounce to the main actor from the callback automatically. So, the best option kinda depends on where you’re writing code like this. If it’s an app, like the view controller demo you posted, then I think moving to Swift 6.2 and enabling default m

First up, let me correct a common misconception: The Secure Enclave doesn’t store keys [1]. Rather, it wraps the key in such a way that only it can unwrap it and use it. It’s then up to you as to where you want to store the wrapped key. A common choice is the keychain, but you could just as easily write the wrapped key to a file. As to whether you can access the SE from a daemon, my understanding is that this isn’t supported, although I’m working to confirm that in a different context. But before we start down the SE path, I want to clarify this: [quote='804612021, chapo213, /thread/804612, /profile/chapo213'] non-spoofable proof of machine identity so a remote management server [/quote] What do you mean by “non-spoofable”? Specifically, who are you trying to protect against? Bad actors on the network? Bad actors on that specific Mac? Or users on the Mac? This is important because, in my experience, trying to protect yourself from the user is a mug’s game [2], while trying to protect yourself from bad actors

It looks like one of my colleagues answered this in the new thread you created. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It looks like one of my colleagues answered this in the new thread you created. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com