“codesign”

I'm trying to automate the building of an ipa via jenkins for testflight/app store with automatic code signing enabled.Note: Switching to manual code signing does not work. This post explains that issue perfectly.https://forums.developer.apple.com/message/181305#181305No solution provided.Googling around the recommended way appears to be, build an archive and then export.I can do this via xcode and the ipa can be successfully uploaded to testflight. But that does not lend itself toautomating the process. I found xcodebuild can be use to automate the archive and export.The following commands results in a ipa. But uploading fails because a subproject/Extensions is not properly signed. Which unfortunately isconsisted with the manual signing issue.xcodebuild archive -project myapp.xcodeproj -scheme myapp -archivePath build/archive/name.xcarchivexcodebuild -exportArchive -archivePath build/archive/Name.xcarchive -exportPath build/Name -exportFormat ipa -exportProvisioningProfile Valid Dist profileFew other details

Xcdoe version: Version 8.0 (8A218a), and I compile code using Swift2.3.I want upload to app to app strore, build archive is succesed, but When I click validate or Export on the archive, I got this error:An error occurred during validation Codesign failedThe I click the show logs button , I can see these logs:1. IDEDistribution.critical.log2016-11-12 05:08:29 +0000 [MT] Presenting: Error Domain=IDEFoundationErrorDomain Code=1 Codesign failed UserInfo={NSLocalizedDescription=Codesign failed}2. IDEDistribution.standard.loginvalid resource directory (directory or signature have been modified) invalid resource directory (directory or signature have been modified), This is a important message I think.It seems the error is occur when codesign the framwork. I'm sure I'm using right certificates.

Hello Everyone!I need you help - I tried to solve that problem by myself however I stuck for few days without any results.After changing systme from Maverick to Sierra I noticed problem with compiling my project.Signing Identity: Mac Developer: Przemyslaw Cybulski (YL6DQ9DAW9) /usr/bin/codesign --force --sign F176598F9C9A325C6555AC0D5E68E9F72450079B --timestamp=none /Users/przemekcybulski/Library/Developer/Xcode/DerivedData/Kore5th_1.4G_Beta-gtqmuluibqaumactalwsmjfmkinq/Build/Products/Release/Kore5th_1.4G_Beta_ObjC.app/Users/przemekcybulski/Library/Developer/Xcode/DerivedData/Kore5th_1.4G_Beta-gtqmuluibqaumactalwsmjfmkinq/Build/Products/Release/Kore5th_1.4G_Beta_ObjC.app: resource fork, Finder information, or similar detritus not allowedCommand /usr/bin/codesign failed with exit code 1I tried to clean project, removed some missed pictures and references.I checked frameworks and libraries - everything is fine.Thank you for your help.RegardsPrzemek

Hey there-I'm writing some software to perform hashing of installed applications, and want to ignore Apple's preloaded (SIP protected) applications, so that I don't get false alarms when a user upgrades macOS (they're sufficiently protected already). Is there any way to programmatically determine which application paths are protected by SIP, or a test that doesn't involve trying to write to them? I had initially thought that examining the codesign for Software Signing would be sufficient, but as it turns out some components of Xcode (such as ld) are also signed with that cert. I couldn't find a sandbox profile anywhere referencing these either.Jonathan

When trying to build two objective C apps under Xcode 8.1 I get an error:resource fork, Finder information, or similar detritus not allowedCommand /usr/bin/codesign failed with exit code 1Following the advice I found on this forum I went to the termial app and executedMac-Pro:~ bruce$ cd My Projects/PerPuzzleMac-Pro:PerPuzzle bruce$ xattr -rcMac-Pro:PerPuzzle bruce$ cd DerivedDataMac-Pro:DerivedData bruce$ xattr -rcThis procedure had no effect.Does anyone have any advice on how I might proceed?

I had to rebuild my iMac a few months ago and I restored from my Time Machine backup.I now need to make a change to an app but what used to compile without error is now failing at the codesign step with: Signing Identity: -As far as I can see, all of the account profiles are valid with expiry dates in the future. The only 'odd' thing is that some have a 'Download' button in the 'Action' column of the 'Provisioning Profiles' seciotn of the account details - when I select the Download All Profiles button, they turn grey but never seem to download or disappear (even after aiting for several hours!). Looking at the 'developer' web page, all of my certificates and provisioning profiles are all active.Any ideas welcomedThanksSusan

We have a non-XCode application using a custom build process that produces an app bundle, and we'd like to sign it to make it work nicely with Gatekeeper. We created a Developer ID, generate a certificate for distribution outside of the Mac App Store with it, everything worked fine. Now, we want to sign the code using the codesign command-line utility. But it doesn't work; trying to run the command:codesign -s Developer ID Application: ... --deep -v OurApplication.appalways produces the error:OurApplication.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: /path/to/OurApplication.app/Contents/MacOS/SomeDir/SomeDir-1.5The SomeDir/SomeDir-1.5 path is created by our build process and basically has to be there for the application to run.Any idea what's going on here? Or any hint on how I can get any additional information? The error message is not really informative…Thanks.

(I posted this in the Distribution >> App Submission and Review forum 2 days ago but it has not received a response. Trying here...)I had to rebuild my iMac a few months ago and I restored from my Time Machine backup.I now need to make a change to an app but what used to compile without error is now failing at the codesign step with:Signing Identity: -As far as I can see, all of the account profiles are valid with expiry dates in the future. The only 'odd' thing is that some have a 'Download' button in the 'Action' column of the 'Provisioning Profiles' seciotn of the account details - when I select the Download All Profiles button, they turn grey but never seem to download or disappear (even after aiting for several hours!). Looking at the 'developer' web page, all of my certificates and provisioning profiles are all active.Any ideas welcomedThanksSusan

I created a question on StackOverflow.Everytime I'm running my projects on a device, it takes at least 20 minutes to compile, because of this command used in the framework.sh script of Cocoapods:/usr/bin/codesign --force --sign ${EXPANDED_CODE_SIGN_IDENTITY} ${OTHER_CODE_SIGN_FLAGS} --preserve-metadata=identifier,entitlements $1When I open the Console app of my macbook, I can see tons and tons of logs with signcode as a search term.The thing here is that there is no volumes called ToutSaufVac.Any idea how to fix this?I'm working on Sierra (10.12.1) and with Xcode 8.1 (8B62)

Still trying to codesign my application using a custom build process (no XCode here). I think I found out the reason why codesign doesn't like my application bundle: it issues an error at each directory name containing a dot, apparently thinking it's some sort of bundle. The problem is, some of these directories are used by a library which will look them up with such a name, so I really can't rename them easily.Is there a workaround for this? Is there any way to tell codesign to just consider directories with a dot in their name as just directories, and not expect anything special in them?Thanks.