> On 2014 Oct 29, at 18:05, Stephen Kay <[email protected]> wrote: > > Why would I get "main executable failed strict validation" on an unsigned > app, yet it allows me to replace a v1 signature with no errors?
I don’t know. Maybe the new codesign tool doesn’t know how to find all of the signature-required components of your Carbon app. > OK, but then have I come up with a workaround that allows me to leave > things the way they are? Just codesign it with v1 first and then replace > it with v2? Yes. With Xcode 3.2 and 10.6.8, you should just close your eyes and be happy that it works. Your time would be better spent on a long term plan to move on from there. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
