Xcode: build failed but no error messages

Using Xcode 4.5.1. Our project has been building excellently for the last three months, but suddenly, when I try to build, it says β€œBuild Failure”, but does not show any errors on the exclamation point tab of the triangle and does not explain when it appears up failed.

We have not changed the package identifier or any other project properties. I tried clean and then build, but no luck.

Any ideas on what might cause the problem?

Like this question , but none of the solutions apply.

+80
build xcode
Jan 31 '13 at 12:05
source share
9 answers

Figured it out. A tab with three lines in the speech bubble displays the build log. I think my storyboard file got corrupted during the last git pull.

+145
Jan 31 '13 at 12:11
source share

You can see the reasons for the crash on Report Navigator present in the Navigator window.

  • Open the navigator by clicking the Hide/Show Navigator button located in the upper left part of Xcode.

Screenshot 1

  • Open Report Navigator by clicking on the last button in the list of buttons in the Navigator window.

Screenshot 2

Here you can see the reasons like By Group or By Time

+76
Feb 26 '16 at 7:31
source share

Click the last icon in the upper pane of the left pane in the Xcode window to open secret archive assembly errors.

enter image description here

Most likely, this will be due to the code signing if you can create and run the application, but not in the archive. A further search in your error message should decide that it has now been detected.

+48
Nov 17 '16 at 10:05
source share

Faced with the same problem with xCode 8, the reason was that my Apple Id session expired and xCode was unable to update it due to network connectivity issues after I logged in with my Apple ID in settings. I was able to build normally

+2
Nov 23 '16 at 12:23
source share

If you changed the build system to a new one, return to the standard. He decided for me.

Build system

+2
Sep 13 '17 at 23:24
source share

Click the last icon in the upper pane of the left pane in the Xcode window to open secret archive assembly errors. I had resolution problems that solved for me.

+2
Nov 27 '17 at 7:21
source share

I agree with Jason. You must do something wrong. This is an Xcode error that cannot cause an error. Just get back on your way. The open screens that you edited / opened for the last time. In my case ; was absent in one controller.

+1
Aug 19 '16 at 21:30
source share

Other answers helped me find Report Navigator. There was only one error:

Build operation failed without indicating any errors. Individual build tasks may have failed for unknown reasons. One possible reason: if there are too many (possibly zombic) processes; in this case, rebooting may solve the problem.

I fixed it by closing the Simulator.

0
Jul 04 '17 at 20:01
source share

With me, this was the Dev training profile that I used for this scheme. I changed it to let it go and it worked

0
Oct 30 '17 at 13:31 on
source share



All Articles