Hi everyone! I have what I think is going to be a problem with a very simple solution, but I've reached the limits of my knowledge with this sort of thing. I'm an exhibit/experiential designer trying to build interactive 3D environments with Unreal Engine. Besides being more technically literate than most designers, I don't have very much development knowledge at all. I've packaged my .app through UE and it's running great. The part that I can't seem to wrap my head around is code-signing and notarizing. I believe I've gone through the process correctly but I still get the Gatekeeper dialog box rejecting my app as from an unidentified developer when I run it on a different Mac or download it onto my development Mac and try to run it. I'm using a Developer ID Application certificate installed to Keychain, and ran codesign with that certificate as shown below on every single binary and .dylib file in the package: codesign --deep -f -v -s Developer ID Application: My Name (IDCODE) --entitlement
Search results for
codesign
3,113 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi, I am brand new to Xcode and I keep on getting an error message saying Command CodeSign failed with a nonzero exit code. I am not enrolled in the Apple Developer Program. Does anyone know how to fix this?
Please The flutter app runs good in Simulator, but BUILD FAILED for real iPhone testing.The error is (see details in steps below):Command CodeSign failed with a nonzero exit code I tried to build it inside the Xcode, got the same error. ======================= I looked my login keychain, there are two keys (certificates?): 1. Apple Development: XX XXX (5YYYYYYYYY) 2. Apple Distributiob: XX XXX (5ZZZZZZZZZ) But when building for real iPhone, both keys show up in the log when I use -v option. I am not sure if the Xcode messed up with two keys. Important: how to fix the Codesign error? ===================== I use Automatically manage signing in Xcode. Here are a little more details from the command line: /Users/jrao/Workspace/Flutter/linkbasket/build/ios/Debug-iphoneos/Runner.app/Frameworks/App.framework: errSecInternalComponent Command CodeSign failed with a nonzero exit code /Users/jrao/Workspace/Flutter/linkbasket/build/ios/Debug-iphoneos/Runner.app/Frameworks/Flutter.framework: err
Error code 1 bundle format unrecognized, invalid, or unsuitable Yea, I'm trying to codesign a python app which has been bundled with py2app, but without success. The codesign process logs a whole bunch of files with the above error. def sign_file(file_path, certificate_common_name, hardened_runtime=False): sign_command = [ codesign, -s, certificate_common_name, --force, --timestamp, -v, file_path ] if hardened_runtime: sign_command.append(--options=runtime) success, message = run_command(sign_command) there are literally hundreds of files that fail, and the path may look something like this; code/dist/Impulse.app/Contents/Resources/lib/python3.10/plotly/validators/splom/marker: Needless to say that notorization returns failed Any help would be greatly appreciated. Steven
Topic:
Code Signing
SubTopic:
Notarization
I'm working on a feature for a design mac app that allows designers to export a standalone viewer app that has their design embeded in it. The exported viewer app could then be sent to clients for review. Currently, the feature works by copying a viewer app embeded in the main app's bundle to the user's desktop, and then copying the design file into the viewer (~/Desktop/Viewer.app/Contents/Resources/designFile)This works great, unless the client doesn't have the allow apps from anywhere security setting turned on. If I enable codesigning for the viewer app, codsigning is broken by copying the design file into the app's resources folder. Pre-mavricks you could specify files that codesign should ignore, but this is no longer possible. So my quesiton is this: is there some other way to make this viewer app so that it's codesigned?
I've developed a mobile app in Visual Studio 2022 on Windows 11 on the MAUI platform. I'm Pair to a remote Mac machine to test/debug on an iOS Simulator. I was previously able to test on the remote mac machine simulator with not problems. I added some features including Geolocation and now I get the following error: error MSB6006: codesign exited with code 3. These are the last few lines in the Output window: 1> [xma][info]: Starting remote task execution for 'TriStar.Mobile.DriverPortal': Xamarin.MacDev.Tasks.CodesignVerify 1> [xma][info]: Sending Request Xamarin.Messaging.Build.Contracts.ExecuteTaskMessage to topic xvs/build/17.2.8053/execute-task/TriStar.Mobile.DriverPortal/8f2f6e4002fCodesignVerify 1> [xma][info]: Received Response of Xamarin.Messaging.Build.Contracts.ExecuteTaskMessage to topic build2424827232benbl/+/xvs/build/17.2.8053/execute-task/TriStar.Mobile.DriverPortal/8f2f6e4002fCodesignVerify 1> CodesignVerify: 2024-05-31T17:36:08.1417751-05:00 - Logging messages 1> Envi
Topic:
Code Signing
SubTopic:
General
I'm trying to sign my app but after signing and running a few commands, I'm completely lost. After signing, I check the result by running: spctl -a -vv ~/MyApp.app Unfortunately, I only get /Users/rwardrup/Desktop/MyApp.app: rejected origin=Apple Distribution: Robert Wardrup (##########) Additionally, if I run codesign -vv --deep-verify I get /Users/rwardrup/Desktop/MyApp.app: valid on disk /Users/rwardrup/Desktop/MyApp.app: satisfies its Designated Requirement The app runs as expected and everything, I just can't get spctl to give a satisfactory answer. I'm signing everything by running this in my script: find ~/Desktop/MyApp.app/Contents/Resources/* | xargs -I $ codesign -f --verify --sign ########## $ find ~/Desktop/MyApp.app -name *.dylib | xargs -I $ codesign -f --verify --sign ########## $ find ~/Desktop/MyApp.app -name *.framework | xargs -I $ codesign -f --verify --sign ########## $ codesign -f --sign ########## --options runtime --timestamp --verbose --ent
Signed on 10.11.5 command-line application doesn't pass the verification just after signing - spctl gives me an obsolete resource envelope error. So it doesn't run.I sign with the command:codesign -fs Developer ID Application: MyCompany path/to/cmd_appOn 10.11.1 and 10.10 (only we have) - GateKeeper allows to start it and application works properly.Are any new parameters or rules to codesign command line applications for running on 10.11.5?
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Signing Certificates
Provisioning Profiles
Hi all, in order to submit my application to the notarization system, in my continuous integration tools I used to run the following command to sign my app: codesign -s $SIGNKEY_NAME --timestamp --options runtime myApp.app --deep The command was working fine in the last year and allow me to notarize the application succesfully. Starting from the last week the same code is now throwing a timestamp error: A timestamp was expected but was not found. And i don't know why, since nothing relevant has been changed. UPDATE: If i try to run the same command but with the option --timestamp=none everything works fine : myApp.app: signed app bundle with Mach-O thin I though that there are some issues with the connectivity with the timestamp server, could be? I don't know if this can help, but if i try to ping timestamp.apple.com i have the following PING timestamp.pki-apple.com.akadns.net (17.32.213.129): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 R
Sparkle.framework gets signed by an Archive pre-action script defined in my Release scheme: LOCATION=${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH} codesign --verbose --timestamp --force --deep -o runtime --sign ${CODE_SIGN_IDENTITY} $LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/AutoUpdate.app codesign --verbose --timestamp --force -o runtime --sign ${CODE_SIGN_IDENTITY} $LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A xcodebuild however seems to ignore the signing results (ie none of Sparkle's files are signed in the resulting archive) when running xcodebuild with the following arguments: xcodebuild -scheme Release -configuration Release -archivePath App.xcarchive archive Notarizing my app therefore fails. What am I doing wrong here? I also tried signing using a Run Script phase during build, which resulted in No such file or directory errors.
can someone please help me, I am new to using Xcode and SwiftUI, I recently updated to Sonoma and now am having issues building and running projects. i am creating this for a class assignment due in a few days any help is appreciated. currently I am having this error upon simply creating a new file: Showing Recent Errors Only Build target ImageApp of project ImageApp with configuration Debug CodeSign /Users/carina/Library/Developer/Xcode/DerivedData/ImageApp-braozmttxaqevhglgrebdherlmlh/Build/Intermediates.noindex/Previews/ImageApp/Products/Debug/ImageApp.app (in target 'ImageApp' from project 'ImageApp') cd /Users/carina/Desktop/AME 430/ImageApp Signing Identity: Apple Development: [my email] (B75Q73AMVQ) /usr/bin/codesign --force --sign 9AFE419D4A362429289B899DECCFB65E5F68E135 -o runtime --entitlements /Users/carina/Library/Developer/Xcode/DerivedData/ImageApp-braozmttxaqevhglgrebdherlmlh/Build/Intermediates.noindex/Previews/ImageApp/Intermediates.noindex/ImageApp.build/Debug/ImageApp.bui
After Upgrading to Xcode 13 my Builds are failing with Command CodeSign failed with a nonzero exit code. My app is in version 3.4.4. While trying to build version 3.4.5 for Mac we have started to get this error: Command CodeSign failed with a nonzero exit code Have tried everything people have said in this and other forums: Clean build folder; Restart Xcode Add --deep to Other Code Signing Flags Revalidate all Certificates Manual and Auto Signing The unsigned executable works fine. I am Evan able to Sign it manually and distribute locally. For Store Submission we need this step to succeed. Will appreciate help from Apple Technical Support This started happening with Xcode 13.
I've seen this error in the past but it's come back. 😟Here's what it spits out (redacted)CodeSign ~/Library/Developer/Xcode/DerivedData/...BundleName.bundle cd ~/.../Pods export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=... Signing Identity: - /usr/bin/codesign --force --sign - --timestamp=none ~/Library/Developer/Xcode/DerivedData/...BundleName.bundle ~/Library/Developer/Xcode/DerivedData/...BundleName.bundle: bundle format unrecognized, invalid, or unsuitable Command /usr/bin/codesign failed with exit code 1Have development pod with .bundle packages in the src. Those packages have directories named Resources. If we change it to anything else, the problem goes away.Worked fine on Xcode 8.0
Hi,After we made changes for apple notarization, I cannot seem to re-place a binary for debugging.[This are all terminal binaries, not apps]executable A is linked with library B, both are codesingned withcodesign -f -o runtime -s identity <binary>and, are runnign fine.Now, for debugging if I make a change in B and replace it, now A is killed right away with errorException Type: EXC_BAD_ACCESS (Code Signature Invalid)Exception Codes: 0x0000000000000032, 0x0000000103082000Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace CODESIGNING, Code 0x2Application Specific Information:dyld: in dlopen()<path to library B>even if I add entitlement get-task-allow to executable A, it's still same.What can I do, what am I missing?
I spent 20 minutes trying to figure out why codesigning was failing -- I had the pf block set up correctly, my keychains were unlocked, and then, eventually, it occurred to me, hey, maybe an IP address changed, so I disabled IPv6 except for link local, and then amazingly, it went back to working. I filed FB13706261 over a year ago. This is ridiculous.