Skip to content
This repository has been archived by the owner on Dec 6, 2019. It is now read-only.

Document the "Unsign xcodebuild too?" option. #8

Closed
jklausa opened this issue Sep 16, 2016 · 2 comments
Closed

Document the "Unsign xcodebuild too?" option. #8

jklausa opened this issue Sep 16, 2016 · 2 comments

Comments

@jklausa
Copy link

jklausa commented Sep 16, 2016

Your awesome gem is helpful, but the prompt about unsigning xcodebuild is not :)

Just prompting the question without giving any context what potential consequences are there is not very helpful. I'd be happy to submit a PR if you could explain to me in plain english what happens if I let it/prevent it from unsigning it.

Thanks a lot for this gem!

@inket
Copy link
Owner

inket commented Sep 18, 2016

Hi!

If xcodebuild is signed, running it from the command-line (whether for simply building, running tests or through carthage build) will print warnings about not being able to load plugins because of library validation.

Unsigning it would hide those warnings, and technically also allow for plugins that modify xcodebuild's functions.

The binary that gets unsigned is /Applications/Xcode-unsigned.app/Contents/Developer/usr/bin/xcodebuild and you would need to set the toolchain path to Xcode-unsigned to be able to run it:

$ sudo xcode-select -s /Applications/Xcode-unsigned.app/Contents/Developer

@inket
Copy link
Owner

inket commented Oct 26, 2016

Added info to README about this and linked to this issue. Closing this now. Thanks for bringing it up!

@inket inket closed this as completed Oct 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants