“codesign”

We have an app that was provided to us by a third-party developer. I do not have access to the source code or the xcodeproj file for this app. I have re-signed the app, using the iResign utility, with a distribution certificate and an App Store provisioning profile that I created in our developer account. I extracted the entitlements.plist file from the app using codesign, and updated it, replacing the third-party developer's Team ID and bundle ID, and assigned it an bundle ID that is from an App ID that I also created in the developer portal. Our team ID is 12A345BCDE, and the bundle ID value is com.myiosapp. The iResign process is successful. I have the Change ID box checked on iResign, with the new bundle ID value provided in the field.When I submit the app using Application Loader, I get multiple instances of this error:ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that arenot supported on iOS. Specifically, value '12A3

I'm trying to add a small PNG file to my project and the build resuts in a codesign error:Debug/Example.app: resource fork, Finder information, or similar detritus not allowed Command /usr/bin/codesign failed with exit code 1I can add the same image as JPG format and the project compiles/runs just fine.What would cause this issue ... does Xcode for some reason dislike PNG images? I found this thread that sounded similar: https://forums.developer.apple.com/thread/68489but would like to understand what cuases this issue before I start running unknown utilities to fix things I can't explain.Thanks,

I’m needing to create a Production Developer ID certificate, to sign an app that will be outside the App Store distribution as outlined here: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.htmlUnder the section titled Creating Additional Developer ID Certificates”, note that Step 4 mentions to “select the Developer ID under Production, and click Continue.”:However when I get to this step in the instructions, I'm seeing only this:There is either a gap in the documentation or my permissions aren't set to create this - but not sure.Can someone suggest how I proceed? FWIW: I should also note that the App we are building is developed around Eclipse RCP - and hence doesn't use XCode. We need to sign to get around Gatekeeper restrictions in OS X 10.12.x. All codesigning is happening via CLI.Thanks,- JK

Hi, getting seg faults every time I try and sign my apps with the codesign -f -s Developer ID Application command.I've recently upgraded to Sierra and my membership has renewed so I had to renew my certs - unfortunately both of these happened at the same time so I'm not sure which may have contributed to the issue...Anyone else seeing these issues? thx

Hi, I built simple application in XCode (version 8.3) on OSX Sierra. Type is Application Bundle so output is .app. It is signed with my Signing Certificate, without provisioning profile and without any Code Signing Entitlements (all Capabilities are OFF). Everything seems to be working, codesign shows it as valid, but when I check builded .app with spctl -avv MyApp.app the output is:MyApp.app: rejected (the code is valid but does not seem to be an app)origin=(there is correct Developer ID Application with correct code).Application is running without problems on my computer but on other machine with OSX Sierra it is stopped by the gatekeeper due to developer identitty.I think I'm missing something in XCode settings. Can somebody give me an advice what I am doing wrong?

Hello everyone,Xcode gives me this error when I try to run my app on the simulator.- Command /usr/bin/codesign failed with exit code 1I've been looking up articles dealing with provisioning profiles and so forth, and from what I'm able to see, issues pertaining to provisioning profiles and certificates are supposed to be fixed automatically.Any ideas?Andy

We built an app that uses openssl to validate a receipt.We added OpenSSL statically as a framework (libcrypto.a and libssl.a).We added a Run Script build phase that signs those two frameworks with our 3rd Party Mac Developer Application: CompanyName.Through Xcode, Validation passed normally.After the upload to the Mac App Store, we received an email from iTunes Connect that says we have issues with the delivery.Specifically, the email says:code object is not signed at all In subcomponent: com.companyname.AppName.pkg/Payload/AppName.app/Contents/Frameworks/libcrypto.aTo check what I'm delivering, I exported a .pkg for Mac App Store Deployment. I simulated a Store Installation in /Applications with:sudo installer -store -pkg /Users/path/to/MASDeployed.pkg -target /Output:installer: Note: running installer as an admin user (instead of root) gives better Mac App Store fidelity installer: AppName.pkg has valid signature for submission: 3rd Party Mac Developer Installer: CompanyName installer: Installation Check: P

I am trying to distribute an application which is codesigned, and worked fine for previous versions of OS X, but is now failing with the identity of the developer cannot be confirmed error message on OSX Sierra. The app bundle looks like it is correctly signed, and the DMG is also signed.Any suggestions on how to troubleshoot this problem?Thanks!-Jonathan

We've been having troubles preventing the popup from showing in our App Store app. The app is an Electron app, which means we're not using XCode to codesign it, but we've been able tyo get a normal (non App Store) signed version to work properly by using a requirements string. The app uses helper apps, and we've ensured that those are properly signed along with any relevant binaries. We used the com.apple.security.application-groups key and com.apple.security.inherit for child entitlements. And verified that these are being included properly.Part of the problem is there doesn't seem to be a way to test this aspect before submitting to the App Store. We can't test apps signed with a distribution certificate, and apps signed with a developer certificate will always pop up the warning anyways.