Search results for

codesign

3,113 results found

Post

Replies

Boosts

Views

Activity

Codesign in a CI environment (Sequoia)
Can someone please describe what is necessary to perform signing using codesign in a system that runs as LaunchDaemon. All workarounds like placing the codesigning cert + private key a custom keychain and unlock it in the session of the LaunchDaemon doesn't work anymore on Sequoia. Or are there alternatives for signing MachO binaries without codesign?
Topic: Code Signing SubTopic: General
1
0
412
Feb ’25
Reply to xattr -c not removing com.apple.FinderInfo attribute from Xcode files
There’s two parts to this: Why can’t you remove the Finder info attribute? Why are you trying to remove the Finder info attribute? IMO the second part is the interesting one. Apropos that you wrote: [quote='774781021, jsflack, /thread/774781, /profile/jsflack'] I came to this problem because my Xcode project was failing to build due to the error resource fork, Finder information, or similar detritus not allowed [/quote] Blinding remove all extended attributes in the hope that’ll fix this problem is not a great idea. Rather, you should track down how the extended attributes got there in the first place [1], and remove them at the source. If you look at the build transcript (see Command [something] failed with a nonzero exit code), what is the exact output from codesign? If you repeat that command from Terminal, do you get the same output? Usually that’s the case, but it’s always good to confirm. If you, so can start running experiments to work out exactly what it’s complaining about. One option is to
Feb ’25
Reply to Couldn't read USB device endpoints on MacOS15.3
Hi Kevin, Yes, We have included the com.apple.security.device.usb entitlement and following are the details- codesign -d --entitlements :- Refresh Pro.app/Contents/Library/LaunchServices/com.prograde.pgdrefreshpro.helpertool Executable=/Applications/Refresh Pro.app/Contents/Library/LaunchServices/com.prograde.pgdrefreshpro.helpertool warning: Specifying ':' in the path is deprecated and will not work in a future release com.apple.security.cs.allow-dyld-environment-variablescom.apple.security.cs.allow-jitcom.apple.security.cs.allow-unsigned-executable-memorycom.apple.security.cs.disable-library-validationcom.apple.security.device.usb``` codesign -d --entitlements :- Refresh Pro.app/ Executable=/Applications/Refresh Pro.app/Contents/MacOS/Refresh Pro warning: Specifying ':' in the path is deprecated and will not work in a future release com.apple.security.cs.allow-dyld-environment-variablescom.apple.security.cs.allow-jitcom.apple.security.cs.allow-unsigned-executable-memorycom.apple.security.c
Topic: App & System Services SubTopic: Core OS Tags:
Feb ’25
Unable to validate with app sandbox issues
My app is a Safari extension. When trying to validate the app, I get the following error: App sandbox not enabled. The following executables must include the com.apple.security.app-sandbox entitlement with a Boolean value of true in the entitlements property list: [( app.rango.Rango.pkg/Payload/Rango for Safari.app/Contents/MacOS/Rango for Safari )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. I don't know why this is happening. I have app sandbox enabled in both the app and the extension target. I have both entitlement files. When executing codesign -d --entitlements :- /path/to/binary I get the following: com.apple.security.app-sandboxcom.apple.security.files.user-selected.read-onlycom.apple.security.get-task-allowcom.apple.security.network.client If I check on Activity Monitor, on the sandbox column it shows true. I have no idea why I keep getting this error when all indicates that the app is actually sandb
4
0
505
Feb ’25
Issues with Notarization and Stapling
Hello, I am trying without luck to create a .dmg or .pkg for my electron app that can be opened by any user on a mac. Every time I fail. All is happening by the same pattern. Here is the last try with creating a .pkg instead of .dmg. The app is built and it is signed correctly (I suppose) codesign --verify --verbose=1 dist/mac-universal/VIVIDTIME.app dist/mac-universal/VIVIDTIME.app: valid on disk dist/mac-universal/VIVIDTIME.app: satisfies its Designated Requirement I created a .pkg pkgbuild --root dist/mac-universal/VIVIDTIME.app --install-location /Applications/VIVIDTIME.app --identifier app.vividtime.mac --version 1.1.0 --sign Developer ID Installer: Pavel Bochkov-Rastopchin (2QKDCTR5Y3) dist/VIVIDTIME.pkg pkgbuild: Inferring bundle components from contents of dist/mac-universal/VIVIDTIME.app pkgbuild: Adding component at Contents/Frameworks/Mantle.framework pkgbuild: Adding component at Contents/Frameworks/VIVIDTIME Helper.app pkgbuild: Adding component at Contents/Frameworks/VIVIDTIME Help
25
0
771
Feb ’25
Reply to Unable to Code Sign: errSecInternalComponent on macOS Sonoma 15.3
I have set trust back to system defaults and I have the DeveloperIDG2CA intermediate installed and im still unable to sign MyTrue. I was trying to follow your troubleshooting page but I fail at the first obstacle unlocking keychain and trying to sign Mytrue still results in a error % security unlock-keychain password to unlock default: % codesign --force --timestamp --sign my hash MyTrue MyTrue: replacing existing signature Warning: unable to build chain to self-signed root for signer Developer ID Application: ,,,,,,, MyTrue: errSecInternalComponent im very aware im probably doing something wrong I am at a loss. Thank you for your reply
Feb ’25
Reply to local network access dialogue does not appear when launching binary from swift package from xcode
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. Moreover xctest was able to present local network access dialogue when also run from Xcode it seems. Xcode’s testing infrastructure is interesting because it runs with or without a host application. With a host application, the test inherits the privileges of that app. Without a host application things get weird. So it can be said Im just experimenting Right, cool. That matters because it affects what workarounds you have access to. I tried some things here in my office and the results were… well… interesting: An Xcode project created from the macOS > Command Line Tool template just works. A Swift package created from the macOS > Command-Line Tool template prompts, but then fails to get access. In both cases you can get things to work by choosing Product > Scheme > Edit Scheme and then selecting Options > Console > Terminal. This runs the tool in Terminal, so it inheri
Feb ’25
Unable to Code Sign: errSecInternalComponent on macOS Sonoma 15.3
Hi Developer Community, I'm encountering persistent code signing failures on macOS Sonoma 15.3 with a valid Developer ID Application certificate. The error occurs consistently across multiple certificate regenerations and various troubleshooting approaches. Environment macOS Version: Sonoma 15.3 Developer Account Type: Developer ID Certificate Type: Developer ID Application Certificate Details: Developer ID Application certificate valid until 2027 Using SHA-256 with RSA Encryption Certificate shows as valid in Keychain Access with associated private key Error Message Warning: unable to build chain to self-signed root for signer Developer ID Application: [my certificate] [filename]: errSecInternalComponent Steps to Reproduce Install certificate chain in order: Apple Root CA (System keychain) Apple WWDR CA (System keychain) Developer ID CA (System keychain) Developer ID Application certificate (Login keychain) Verify certificate installation: security find-identity -v -p codesigning Result shows valid
3
0
413
Feb ’25
Mismatch of teamID while creating development certificate
Hi Team, I have created multiple certificates for macOS application. Below are the certificates created- Apple Development Certificate DeveloperID Installer Certificate Apple Distribution Certificate others certificates Later, I have imported the all these above certificates in keychain-access. Now, I tried to compile the code through Xcode. I am getting error for code signing certificate. Warning: unable to build chain to self-signed root for signer Apple Development: Amit (M2WMF2YERI)” .... Command CodeSign failed with a nonzero exit code When I checked the TeamID of User(Amit) I can see that his current TeamID is [P8ZW3W9R2Q]. There is mismatch of teamID in apple development certificate generation. Note- All certificates are generated with current TeamID[P8ZW3W9R2Q] of user (Amit) except Apple Development certificate which has been generated with TeamID [M2WMF2YERI] which is generated with old TeamID of user (Amit). I attempted to generate the apple development certificate multiple times but it is
1
0
380
Feb ’25
Mismatch of TeamID while creating development certificate
Hi Team, I have created multiple certificates for macOS application. Below are the certificates created- Apple Development Certificate DeveloperID Installer Certificate Apple Distribution Certificate others certificates Later, I have imported the all these above certificates in keychain-access. Now, I tried to compile the code through Xcode. I am getting error for code signing certificate. Warning: unable to build chain to self-signed root for signer Apple Development: Amit (M2WMF2YERI)” .... Command CodeSign failed with a nonzero exit code When I checked the TeamID of User(Amit) I can see that his current TeamID is [P8ZW3W9R2Q]. There is mismatch of teamID in apple development certificate generation. Note- All certificates are generated with current TeamID[P8ZW3W9R2Q] of user (Amit) except Apple Development certificate which has been generated with TeamID [M2WMF2YERI] which is generated with old TeamID of user (Amit). I attempted to generate the apple development certificate multiple times but it is
1
0
387
Feb ’25
any pyqt user here? can you tech me how to make a perfect app
i was complete my program, and export a mac app already it work ok in my macmini, but if i want send it to app store, that i have no way now i still do not know how to make this app perfect like, when i use pyinstaller to build this app, is there any info or elements need make with? i can sign my app now, even i use codesign -dvvv my.app to check the sign, it is also ok, there no any feedback said it anything wrong. so, any master know fix app sign or any infoplist please tech me... help
0
0
233
Feb ’25
Could not find the main bundle or the Info.plist is missing a CFBundleIdentifier
I had a standalone python application (created with pyinstaller) which was working perfectly alone. This macOS application was created in VS. I later decided to improve the application by implementing some Swift features (Subscription Manager). This required me to write a brief Swift file (Subscription Management) in XCode which the Python file called on. Python Standalone Application Calling Swift : # Function to check if the user has a valid subscription def check_subscription(): subscription_manager_path = /Users/isseyyohannes/Library/Developer/Xcode/DerivedData/SubscriptionManager2-ezwjnnjruizvamaesqighyoxljmy/Build/Products/Debug/SubscriptionManager2 # Adjust path try: result = subprocess.run([subscription_manager_path], capture_output=True, text=True, check=True) return VALID_SUBSCRIPTION in result.stdout # Return True if valid, False otherwise except subprocess.CalledProcessError as e: print(fError checking subscription: {e}) return False # Return False if there's an issue However, when I try to run xc
1
0
321
Feb ’25
Error with downloading SAP
Hi! I am a 3rd year accounting student trying to install an SAP gui onto my brand new Macbook Air. Every time I download the app, it refuses to open and pops up with this error. CODESIGNING 1 Taskgated Invalid Signature I have Java installed for it and have followed my professor's directions, so it should be working. Can someone help me?
1
0
158
Feb ’25
Reply to LaunchCodeRequirement alternatives
No. Well, if there were, that’d be a significant security bug (-: Nice! Thanks for confirming that! At least we can rely on LaunchCodeRequirement on macOS 14.4+. Not really. As you’ve determined, from the parent’s perspective it looks like the process died very early with a SIGKILL. There’s no additional information that comes along with that termination status. You could turn around and run code signing checks on the executable, but at best that only gives you indirect information. Well, I expected process.run() to throw an exception I could catch and learn from it what exactly has happened in case of failed codesign requirement check. I can submit a feature request if you think it's doable.
Topic: Code Signing SubTopic: General
Feb ’25