Search results for

Apple Maps Guides

149,836 results found

Post

Replies

Boosts

Views

Activity

code signature validation failed fatally - Unsatisfied Entitlements
Hello, We have a working application with several entitlements - com.apple.developer.endpoint-security.client and com.apple.developer.team-identifier. Recently, the Developer ID signing certificate expired and we created a new one according to the instructions on the website. Also the provisioning profile for those entitlements expired so we edited it to use the new certificate. We built using xcodebuild in a script and signed with codesign, We supply the certificate id and the entitlement in a plist file like this : codesign --timestamp --force --sign ${application_signature} --options=runtime ${obj} --entitlements ${SR_ENTITLEMENT_PATH} (those env vars hold the correct values for the cert id and plist path as far as we checked). The signing works and looks ok with codesign -dvvv: (XXXX replaces the real file name for privacy) Signature size=9050 Authority=Developer ID Application: XXXXXX. (XXXXX) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=16 Oct 2025 at 11:09:5
1
0
52
3d
Reply to Developer ID Application Certificate Expires in 30 Days?
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
3d
Reply to DeviceDiscoveryUI and Bonjour for iOS
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
3d
Reply to bundle ID
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
3d
Reply to Crashes because main actor isolated closures are called on a background thread with `DispatchGroup.notify`, but no compiler warnings
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
3d
Reply to Creating machine identifier to be used by daemon based app
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
Topic: Privacy & Security SubTopic: General Tags:
3d
Creating machine identifier to be used by daemon based app
I am developing a daemon-based product that needs a cryptographic, non-spoofable proof of machine identity so a remote management server can grant permissions based on the physical machine. I was thinking to create a signing key in the Secure Enclave and use a certificate signed by that key as the machine identity. The problem is that the Secure Enclave key I can create is only accessible from user context, while my product runs as a system daemon and must not rely on user processes or launchAgents. Could you please advise on the recommended Apple-supported approaches for this use case ? Specifically, Is there a supported way for a system daemon to generate and use an unremovable Secure Enclave key during phases like the pre-logon, that doesn't have non user context (only the my application which created this key/certificate will have permission to use/delete it) If Secure Enclave access from a daemon is not supported, what Apple-recommended alternatives exist for providing a hardware-backed
1
0
278
3d
AVB Support for the AVnu MILAN Conventions
The AVB AVnu MILAN Convention has a groweing Population. Many big companies (Cisco, Meyer Sound, d&b Audio, l‘acoustics, Presonus, digico etc.) implements the AVB AVnu Milan Standards. Is there a plan on the Apple side to also implement AVnu Milan on top of the AVB Protocol? The advantage for Apple Sound would be a great Integration in the professionell Audio market and a more stable intergration on top of the AVB protocol. The atdecc work, but Not that stable.
1
0
97
3d