10.10.3 GM, Codesign and --deep

Sam_Rowlands · April 13, 2015, 9:03am

I’ve just spent the morning tracking down an issue whereby the --deep option for the codesign command has now become flaky under 10.10.3 GM.

If you’re using App Wrapper, I’ve just released an update which handles codesign errors better, if you’re using the “Apple Temp Engine” option and you get error codes 133 or 139, then unselect the “Apple Temp Engine” engine and it will revert back to using App Wrapper’s own engine.

Sascha_S · April 13, 2015, 9:57am

Thank you Sam

Michel_Bujardet · April 13, 2015, 12:09pm

[quote=180058:@Sam Rowlands]I’ve just spent the morning tracking down an issue whereby the --deep option for the codesign command has now become flaky under 10.10.3 GM.

If you’re using App Wrapper, I’ve just released an update which handles codesign errors better, if you’re using the “Apple Temp Engine” option and you get error codes 133 or 139, then unselect the “Apple Temp Engine” engine and it will revert back to using App Wrapper’s own engine.[/quote]

Thank you.I love your update system. Very convenient

Sam_Rowlands · April 13, 2015, 1:31pm

Thanks you guys and you’re most welcome, I’ll modify a future version to handle these errors even more elegantly. In the mean time I thought I’d let people know.

Detlef_Kahner · April 13, 2015, 3:25pm

True. Thanks again for the informations.

Mike_D · June 23, 2015, 9:05pm

I just ran into this problem, but I’m not using AppWrapper, simply trying to do codesign via the command line inside a build script. Is there a robust solution?

See https://forum.xojo.com/7022-problems-with-codesigning-app-for-app-store

Sam_Rowlands · June 24, 2015, 2:08am

HI Michael, give the trial version of App Wrapper a shot. App Wrapper also features it’s own solution for code signing nested code. http://www.ohanaware.com/appwrapper/