signing problem
signing problem
- Subject: signing problem
- From: Scott Ribe <email@hidden>
- Date: Sun, 10 Nov 2013 14:51:25 -0700
Any clues what to look at when codesign says things are fine and storeagent says they are not?
I've recently upgraded from Xcode 3.2.6 to 5.0.1, and am now trying to get an update ready to submit to the MAS. But when I run it to test receipt update, it returns 173 and quits as usual, then does not relaunch and I see this in the terminal:
11/10/13 2:15:29.230 PM storeagent[278]: Unsigned app (/Users/.../foo.app).
But the thing is, that codesign verifies the signature successfully:
codesign --verify --verbose=4 -d /Users/.../foo.app
Executable=/Users/.../foo.app/Contents/MacOS/foo
Identifier=com.my.bundle.id
Format=bundle with Mach-O thin (x86_64)
CodeDirectory v=20100 size=6135 flags=0x0(none) hashes=298+5 location=embedded
Hash type=sha1 size=20
CDHash=1a9ea917bba6a4c16156c6e6fdb2e69487da59ae
Signature size=4395
Authority=3rd Party Mac Developer Application: my cert (B2E75262ZM)
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Nov 10, 2013, 1:03:50 PM
Info.plist entries=24
Sealed Resources version=2 rules=12 files=40
Internal requirements count=1 size=232
I'm in the habit of codesigning via script rather than having Xcode do it, because there are some child items that get put into the app bundle along with their own code signatures (which are also validating just fine, BTW), and some other stuff that goes on, like creating shell appcast files, and zip archives, and so on.
I'm tempted to go ahead and build & sign the package, and try to submit it, to see if I get some more detailed error...
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden