Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when uploading binary: Invalid Signature. Code object is not signed at all Cloudinary.framework/GenerateCLDCryptoModule #6

Open
kyle-ssg opened this issue Aug 6, 2017 · 3 comments

Comments

@kyle-ssg
Copy link

kyle-ssg commented Aug 6, 2017

ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [AccaApp.app/Frameworks/Cloudinary.framework/GenerateCLDCryptoModule] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [AccaApp.app/Frameworks/Cloudinary.framework/GenerateCLDCryptoModule] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

edit: I got around this eventually by deleting GenerateCLDCryptoModule. Not really sure of the root issue, ios codesigning is baffling.

@mchandleraz
Copy link

Hey @kyle-ssg, how exactly did you remove GenerateCLDCryptoModule? When I deleted the directory, my project wouldn't archive any more.

@noumantahir
Copy link

having this same weird issue, tried a few signing certificates but no luck...any help here...?

@noumantahir
Copy link

@mchandleraz removing GenerateCLDCryptoModule does fix the problem...do not remove directory and neither the .swift file...just remove separate GenerateCLDCryptoModule inside folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants