Note that there are some explanatory texts on larger screens.

plurals
  1. POcopyplist failed with exit code 71
    primarykey
    data
    text
    <p>I have an iPhone app that's shipping (<em>vConqr</em> - you should go and buy it :-) ). I build the project on several different machines, including a colleague's, and it's been working fine. However, just recently, on my second dev machine my build fails every time with the error:</p> <p><code> /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copyplist Entitlements.plist --outdir /Code/iPhone/VirtualConquest/build/Debug-iphonesimulator/VirtualConquest.app </code></p> <p><code> error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copyplist' (No such file or directory) </code></p> <p>I've reinstalled XCode - twice! (the second time I deleted the files under /Developer/Library/Xcode first). I've deleted my source tree and checked out of source control fresh. The error persists.</p> <p>The Entitlements.plist file has been there for a couple of weeks, since I started my last beta programme. I can't be sure, but I suspect I had not compiled on my second dev machine since it was added. However, as well as my primary dev machine, it also all builds fine on my colleagues machine, so I'm baffled what the difference can be.</p> <p>I've Googled for the error, but either my Google-Fu is bunk or this is not a common error - I've found no relevant hits.</p> <p>This is really frustrating, not least because I use my second machine as a soak test/ continuous integration machine.</p> <p>Anyone come across the same thing, or have any other suggestions?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload