Search results for

codesign

3,110 results found

Post

Replies

Boosts

Views

Activity

Reply to XPC codesign requirement crashes application
Log output from com.apple.securityd below: 2025-08-29 15:36:50.076408+0200 0x6dc007 Debug 0x0 26936 0 : (libxpcfileprovider.dylib) [:NSXPCConnection] Set code signing requirement with team identifier 2025-08-29 15:36:50.076991+0200 0x6dc007 Default 0x0 26936 0 : (Security) [com.apple.securityd:security_exception] MacOS error: -67052 2025-08-29 15:36:50.078752+0200 0x6dc007 Debug 0x0 26936 0 : (Security) [com.apple.securityd:security_exception] 0 Security 0x000000019fa4ec74 Security::CommonError::LogBacktrace() + 124 2025-08-29 15:36:50.078785+0200 0x6dc007 Debug 0x0 26936 0 : (Security) [com.apple.securityd:security_exception] 1 Security 0x000000019fa4f20c Security::MacOSError::MacOSError(int) + 312 2025-08-29 15:36:50.078800+0200 0x6dc007 Debug 0x0 26936 0 : (Security) [com.apple.securityd:security_exception] 2 Security 0x000000019f92bbd4 Security::CodeSigning::CSError::CSError(int, __CFDictionary const*) + 24 2025-08-29 15:36:50.078810+0200 0x6dc007 Debug 0x0 26936 0 : (Security) [com.apple.securi
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
4w
Certificate Active in Keychain and I think Xcode but Not Recognized by VS Code / Flutter on macOS Tahoe (macOS 15)
Hi, hoping someone can help here. I recently updated my Mac to macOS 15 (Tahoe) and am using Xcode 15+ (possibly 16). I’m working on a Flutter app and testing on a real iPhone device. Here's the situation: I’m using the free Apple Developer account. My signing certificate and provisioning profile both show as valid and active in Keychain and says signing... in Xcode. When I build and run the app from Xcode, it works completely fine on a simulator. But when I try to run the same project from VS Code using flutter run, whether on an simulator phone or my personal iphone, I get a code signing error, specifically: Failed to codesign Flutter.framework with identity... I believe the app is set to use the correct Team ID because it says my name and (team) (my team ID isBDKUKWVRBY), and I can see my certificate in Keychain under My Certificates. What I’ve already tried: flutter clean pod install / pod update Manually selecting my team in Xcode Signing settings Restarting my machine and VS Code Confirming the
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles
1
0
123
Sep ’25
Xcode 16.x crashes immediately on launch - MacBook Pro 15,4 mid-2019
Hardware & OS: MacBook Pro 15,4 (mid-2019) macOS 15.7 (24G222) Apple Hardware Diagnostics: Passed (ADP000) Xcode crashes on every launch attempt with identical CoreSimDeviceIO framework failures. This started after an automatic Xcode update and affects multiple Xcode versions. Versions tested (all crash identically): Xcode 16.0 (26.0/24228) Xcode 16.4 (23792) *Unable to download Xcode 15.4 due to my ios Crash signature: Exception Type: EXC_BAD_ACCESS (SIGKILL Code Signature Invalid) Crashed Thread: 0 (main thread) Crashing Framework: CoreSimDeviceIO.framework Termination Reason: CODESIGNING, Code 2 Invalid Page Troubleshooting completed: Multiple fresh Xcode downloads from Apple Developer portal Security database rebuild and SystemPolicy reset Complete macOS clean reinstall Developer tools reset (xcode-select) NVRAM reset Hardware diagnostics (passed) Additional problem: macOS compatibility enforcement prevents installing Xcode 15.x as a workaround, showing update to latest version errors even fo
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
110
Sep ’25
Reply to CI - Warning: unable to build chain to self-signed root for signer
Thank you for the answer, I already went over this document. I have problems only with SSH and CI. In the logged-in session, application is signed successfully. Steps I took over SSH: % security find-identity -p codesigning Policy: Code Signing Matching identities 1) 4E7CC0830457446B065A4EEA4CE259E9C3F8107C Apple Development: (CSSMERR_TP_CERT_EXPIRED) 2) E89C6BAEF24BCB768B27A482DF05F5C4623977AE Developer ID Application: 3) E89C6BAEF24BCB768B27A482DF05F5C4623977AE Developer ID Application: 3 identities found Valid identities only 1) E89C6BAEF24BCB768B27A482DF05F5C4623977AE Developer ID Application: 2) E89C6BAEF24BCB768B27A482DF05F5C4623977AE Developer ID Application: 2 valid identities found Then, % security list-keychains /Users/ec2-user/Library/Keychains/login.keychain-db /Library/Keychains/System.keychain % security unlock-keychain % codesign -s Developer ID Application... -f test1 test1: replacing existing signature Warning: unable to build chain to self-signed root for signer Develo
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles
Sep ’25
Reply to Accessibility permission in sandboxed app
I’m not able to reverse engineer other developer’s apps on your behalf, but I can offer some general advice. You can tell whether an app is sandboxed using codesign. For example, BBEdit is sandboxed: % codesign -d --entitlements - /Applications/BBEdit.app | grep -A 2 com.apple.security.app-sandbox … [Key] com.apple.security.app-sandbox [Value] [Bool] true but Xcode is not: % codesign -d --entitlements - /Applications/Xcode.app | grep -A 2 com.apple.security.app-sandbox … % Not all Mac App Store apps are sandboxed. Some apps shipped on the store before sandboxing was required. So, when you see an app that does something that’s seemingly impossible, it’s a good idea to check whether it’s actually sandboxed or not. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Sep ’25
Reply to iOS Build Memory Access Issues Causing Crashes
Quinn asked me if I could take a look at this, and I have to say this is going to be a tricky one to track down. Let me start with the basics of what's going on. Pulling from your first crash log, here are the crucial details: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 Exception Codes: 0x0000000000000002, 0x0000000000000000 ... Termination Reason: CODESIGNING 2 Invalid Page ... Thread 4 name: Dispatch queue: assetsQueue Thread 4 Crashed: 0 ??? 0x0 ??? 1 Video Star 0x1012b34b0 __28-[ClipMixerView asyncRender]_block_invoke + 512 2 ...g_rt.asan_ios_dynamic.dylib 0x10559adf4 __wrap_dispatch_async_block_invoke + 196 3 libdispatch.dylib 0x19aacaaac _dispatch_call_block_and_release + 32 4 libdispatch.dylib 0x19aae4584 _dispatch_client_callout + 16 5 libdispatch.dylib 0x19aad32d0 _dispatch_lane_serial_drain + 740 6 libdispatch.dylib 0x19aad3dac _dispatch_lane_invoke + 388 7 libdispatch.dylib 0x19aade1dc _dispatch_root_queue_drain_deferred_wlh + 2
Topic: Developer Tools & Services SubTopic: General Tags:
Sep ’25
Reply to macOS 26 Launch Constraints
OK, so you’re dying from a launch constraint violation. That launch constraint can come from two places: You can bake a constraint into your executable. The code running your daemon can apply a constraint. I believe you’ve eliminated the first possibility, but it’s a good idea to check that. You can do that using codesign: % codesign -d -vvv Desktop/My App.app/Contents/MacOS/com.myCompany.myDaemon … Launch Constraints: … You shouldn’t see a Launch Constraints field. As to the second possibility, there are two things to check: Make sure your daemon is signed with the some code-signing identity as the container app. Move your app from the desktop to a directory that isn’t protected by MAC. MAC-protected directories — like the desktop, Documents folder, and Downloads folder — cause all sorts of weird behaviour. I generally recommend that you run your app from either the Xcode build directory or /Applications. For more info about MAC, see On File System Permissions. Share and Enjoy — Quinn “The
Topic: Code Signing SubTopic: General Tags:
Sep ’25
Dynamically changing app icon
I have a Qt desktop app that I was shipping to users as a dmg on macOS. But now I'll need to kind of rebrand the app to different users, that rebranding involves changing the name and the icon of the app I'm not sure how feasible that is on macOS but here's what I'm thinking: First I'll include all apps for all brands inside the app resources, and instead of shipping the app directly, I will ship and installer (either .pkg or a custom made installer app) that will be responsible for downloading the main app and also setting some environmental variables somewhere so that I can choose the icon from the resources based on the env var values. And then either change the app icon and name from the installer itself, or implement something inside the app that makes it change the icon and name on launch (both icon in finder and in dock) but maybe one of those methods (or both) will break the codesign/notarization of the app so I want to avoid that too I'm not sure if someone has done this before or how feasib
Topic: App & System Services SubTopic: General Tags:
2
0
198
Sep ’25
Reply to SMAppService Sample Code seems broken
And just to verify that it is in fact signed (team ID partially redacted): % codesign -dv /Applications/SMAppServiceSampleCode.app/Contents/Resources/SampleLaunchAgent Executable=/Applications/SMAppServiceSampleCode.app/Contents/Resources/SampleLaunchAgent Identifier=SampleLaunchAgent Format=Mach-O thin (arm64) CodeDirectory v=20400 size=853 flags=0x0(none) hashes=16+7 location=embedded Signature size=4786 Signed Time=Sep 12, 2025 at 2:22:55 PM Info.plist=not bound TeamIdentifier=******9437 Sealed Resources=none Internal requirements count=1 size=188
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Sep ’25
Pkg installation package uploaded to macstore email prompt ITMS-90296
Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager tool Sign the app using @ electron osx sign (version
Topic: Code Signing SubTopic: General Tags:
2
0
599
Nov ’24
Reply to App Groups names are red
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. I am using macOS style that starts with Team ID OK. The Xcode App Group editor is not fully up to speed when it comes to macOS-style app group IDs. The screen shot of your provisioning profile shows the it’s correctly authorising you to use any group matching 2V________.*. And the App Groups editor is showing that you claim two of those groups. That’s all good. Note Regarding the group.com._.MySecurtiyAppGroup, it’s presence isn’t a problem. You’re not claiming access to that group, because the checkbox next it in the App Groups editor isn’t checked. And it’s fine for the profile to authorise you to use groups that you don’t then claim. I suspect that the red indicates that the app group ID you’re claiming isn’t literally in the app group ID listed in the profile. With iOS-style app groups ID that’d be a serious problem. With macOS-style app group IDs, that’s fine because of the wildcar
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Sep ’25
Reply to macOS 26 Launch Constraints
When building as described above, the helper crashes in such a way (Termination Reason: CODESIGNING 4 Launch Constraint Violation) that suggests I need to apply launch constraints to resolve the problem. I had not previously had launch constraints in my project.
Topic: Code Signing SubTopic: General Tags:
Sep ’25