Is this a problem specific to me or is the integration of Unity to XCode fully random? I thought XCode could be scripted better these days but every time I do a build it seems immensely hit or miss.
When you press Prop-B to build from Unity in Xcode, you need to wait until Unity has built the player, XCode has launched and the CLEAN message has come up, followed by the BUILD step has at least started (watch for the Project menu header to blink a second time) before you can use your machine safely for anything else.
Yes, that’s right: Prop-tabbing to another process may interrupt the build, especially if Unity choses that moment to finish building the player and starts trying to talk to XCode.
Additionally, the interprocess communication between Unity and XCode relies on this field’s value inside the XCode app:
DVTPlugInCompatibilityUUID
You can see value of this in the XCode Info.plist file.
Every time Xcode gets revised, Apple puts a new value in this field. Unity doesn’t have it and hence fails to launch XCode smoothly.
Unity stores the field here:
./Unity465f1.app/Contents/PlaybackEngines/iossupport/Tools/OSX/Unity4XC.xcplugin/Contents/Info.plist
You can hand-copy paste the UUID value from XCode’s Info.plist into the Info.plist above to restore functionality, most of the time. Be careful.
2 Likes
Thanks for the in depth reply! I hope/guess that the interprocess communication thing isn’t broken.
But this really means I shouldn’t tab to another application while it’s building?