Shell Script Call Error - Xcode 6

Question

I recently took a project from another developer who was unable to complete the project. The only problem I have is that I cannot get the project to build for the simulator or for the device through Xcode.

The error I am getting is:

Failed to write out copy of document for diagnostics: Failed to write copy of document to path "(null)": Failed to write out copy of document because it has no file URL Showing first 200 notices only **Command /bin/sh failed with exit code 255** 

Can anyone advise where to start looking for a problem with an error?

Additional Information: I am running Xcode 6.0.1. In the "Run Script" "Build Phases" area there is a shell (/ bin / sh) script for Crashlytics.framework that I have not used before .. Not sure if this helps.

EDIT

At the assembly stages, there are two shells. Crashlytics and pods:

 Shell: /bin/sh "${SRCROOT}/Pods/Pods-resources.sh" 

and

 Shell: /bin/sh ./Crashlytics.framework/run xxxxxxxxxxxxx 

Answer 1

Solution . This error was caused by the new version of Xcode (6), which tries to convert xib and is used in some modules used in the project.

Solution 1 - Restart Xcode 5.1 from Member Center: https://developer.apple.com/downloads/index.action

Solution 2 - Update signatures, related files, and the current code base to comply with iOS 8 standards.

Answer 2

I had the same problem as solved. One of my containers (in my case was ICETutorial) - problems with the case due to its xib files. When I uninstalled this module, the application worked perfectly. You may also need to remove the containers and reinstall them; also upgrade them to support iOS8.

Try to check every element of your application; I guess one of them is dealing with this problem.

Hope this helps you.

thanks

Answer 3

I had the same error and found that carthage was not installed. The installed carthage via brew then performed the reconnection. This time, a message to configure Fabric appeared because it was used by the original developer. Installed Fabric and followed their instructions. The problem is gone. Hope this helps.