[MacRuby-devel] MacRuby App Store Code Signing Issue

Elliot Temple curi at curi.us
Thu Oct 13 10:05:27 PDT 2011


Short version:

Getting errors like this emailed from Apple when I submit my app, please help:

> Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/date.rbo is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information.




Details:

I'm submitting a platformer game I made with MacRuby to the Mac App Store. I'm creating a writeup of what I had to do to get it to work which I'll post once it's accepted. I have one issue left I wanted to ask about.

At first I got an automated "invalid binary" rejection and was emailed a very long list of invalid signature errors including one for the main app bundle. This is even though I can see Xcode 4.1 is doing code signing like this

> CodeSign "/Users/curi/Library/Developer/Xcode/DerivedData/Hard_Platformer-bffekhylxcfntifvgtzszieplvfm/ArchiveIntermediates/Deployment/InstallationBuildProductsLocation/Applications/Hard Platformer.app"
>    cd "/Users/curi/c/cs/xcode/Hard Platformer"
>    /usr/bin/codesign --force --sign "3rd Party Mac Developer Application: Elliot Temple" "/Users/curi/Library/Developer/Xcode/DerivedData/Hard_Platformer-bffekhylxcfntifvgtzszieplvfm/ArchiveIntermediates/Deployment/InstallationBuildProductsLocation/Applications/Hard Platformer.app"


So I took the advice here

http://astonj.com/tech/how-to-submit-your-macruby-app-to-the-mac-app-store/

and manually signed it

> codesign -f -s "3rd Party Mac Developer Application: Elliot Temple" Hard\ Platformer.app/


Which looks to me like the same thing Xcode already did, but whatever. That fixed the signature for the main app bundle and avoided automated rejection. A human reviewer will now look at my app :)

But I still got all the other code signing errors emailed to me, and Apple recommends fixing them. Here's some examples:

> Invalid Signature - the nested app bundle MacRuby (Hard Platformer.app/Contents/Frameworks/MacRuby.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information.
> 
> Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/libmacruby.1.9.2.dylib is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to theCode Signing and Application Sandboxing Guide for more information.
> 
> Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/date.rbo is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information.

What should I do about those? Or should I ignore them?

I'm using the MacRuby Nightly from yesterday night, OS X 10.7.2, Xcode 4.1

Thank you for any help.

-- Elliot Temple
http://beginningofinfinity.com/



More information about the MacRuby-devel mailing list