Problems with code sign step
Problems with code sign step
- Subject: Problems with code sign step
- From: Jim Geist <email@hidden>
- Date: Mon, 25 Feb 2013 19:42:41 -0800
Hi all -
We have an iOS project that, as a custom build step, builds a binary blob of data and copies it into the output build folder. This file matches an entry in the resource rules plist so it's part of the set of signed files.
We are seeing the "A signed resource has been added, modified or deleted" message when Xcode tries to deploy to a device. Digging in, the phone is not happy with the code signing, and if I run codesign -v against the .app folder, it complains that the signature on our binary blob is invalid. The timestamp on the signature does not appear to change if the app is redeployed with no code changes (i.e. run it without changing anything, the binary data gets rebuilt, but the code does not.)
This seems odd to me, since in the build log I can see that Xcode is putting --force on the codesign step, which the man page says will make it re-sign even if there is already an existing signature. If I run the same command manually, then the validation step will succeed, but getting Xcode to sign and deploy properly again requires a clean build or changing a source file to force the binary to be relinked.
One non-standard thing we are doing is that our data compression step drops the result directly into the .app folder. I tried putting the file as an output of the build phase, thinking that maybe the build system wasn't seeing the dependency, but it didn't help.
Anyone have suggestions?
Thanks!!
_______________________________________________
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