Skip to content

Instantly share code, notes, and snippets.

@ryjones
Created February 7, 2018 21:42
Show Gist options
  • Save ryjones/3e9a851e92794d67b5e37197608a5f18 to your computer and use it in GitHub Desktop.
Save ryjones/3e9a851e92794d67b5e37197608a5f18 to your computer and use it in GitHub Desktop.
Xcode is killing me.

Xcode is killing me.

I filed a bug in July 2014 that is caused by Xcode over-parsing output of build tools. This breaks our CI systems and creates load on developers asking for exceptions. The radar is 17839697 if you have access.

If you’d like to repro the bug yourself, try this:

Summary:
xcodebuild is examining the output of build tools looking for errors.
Strings with a distinct format will trigger an error, stopping the build.

Steps to Reproduce:
1. install any version of Xcode version 5.1 forward
2. file->new project->OS X->other->external build system
3. take defaults on first screen
4. build tool is “echo”
5. arguments are [:13: 2] (no square brackets, no quotes)
6. build (clover-b)

Expected Results:
7. clean build

Actual Results:
7. build breaks.
8. examine errors: detects :13: 2 as an error, build is broken

Version:
Version 5.1.1 (5B1008)

Very annoying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment