Build service could not start build operation: internal error: failed to send the system info to the build service

L

10

15

I just installed XCode10 and I am trying to run my code on ios8 simulator, in the process I am facing below error

"Build service could not start build operation: internal error: failed to send the system info to the build service"

Leonie answered 21/9, 2018 at 6:24 Comment(2)

That just seems to be a random Xcode 10 thing. I ran an app yesterday, restarted my computer, got this error, cleaned the build and restarted Xcode, and it's fine now, but there seems no rhyme or reason, and I'm not even sure how to file a bug report for something that isn't a problem anymore. – Serdab 25/8, 2019 at 9:56

Having this with Xcode 13.4.1 - very annoying – Congratulatory 22/6, 2022 at 11:32

A

22

I think your Xcode is just in the process of indexing the files. It may take some time to finish but when it's done, just give it a try.

If it's not helpful, try reopening your xcode - it works for me after the indexing process finished.

Adventurous answered 23/9, 2018 at 9:12 Comment(1)

I've recently had XCode10 glitch several times with different bugs (from saying I have 30 syntax errors that did not exist and thereafter compiling to crashing multiple times) and this appears to be another bug... I got the same error as Arti above, and for me, it did not work after restarting XCode, restarting my computer, and waiting for the indexing to finish. Will add again once this fixes / if anything changes – Antinode 20/12, 2018 at 21:10

S

11

No needs to restart system. Just restart Xcode -> clean build fix this issue for me.

Spacing answered 22/10, 2021 at 10:48 Comment(2)

Yes - with Xcode 13.3, simply restarting Xcode resolved this issue. – Cowen 15/4, 2022 at 4:25

Xcode 14.3, this worked for me – Petiole 30/5, 2023 at 3:53

N

8

Restarting my Mac was the only solution for me. Restarting Xcode did not fix. We are back to Microsoft days.

Nicker answered 18/10, 2021 at 21:42 Comment(0)

K

3

Very very strange, you may laugh while reading my answer but restarting my laptop did the trick for me, I was trying to make ios build in my ionic1 app

Kristinkristina answered 29/11, 2019 at 7:2 Comment(1)

yep! restart the mac, did the trick. – Plexus 13/1, 2022 at 19:14

W

1

In my case opening 2 projects at a time using Xcode got the hitch. So I closed all and opened one then it was working fine.

Wheelock answered 23/12, 2021 at 10:51 Comment(1)

This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review – Pennyweight 24/12, 2021 at 7:0

A

0

I commented above but thereafter figured out another possible solution to try. Cleaning the project worked. (I restarted XCode10, my computer, and waited for indexing to finish - neither of these worked for me, at least.)

Command + Shift + K

or equivalently

Product > Clean Build Folder

Antinode answered 20/12, 2018 at 21:14 Comment(0)

A

0

I quit my Xcode and delete some file related to Xcode and empty the bin. Then I open a Xcode project. Its working fine for me.

Anion answered 7/8, 2019 at 7:45 Comment(0)

T

0

I don't think deleting Derived Data, doing a clean, close/reopen Xcode helped, but when I reopened Xcode I had files in "Recovered Resources" folder that appear in the Project Navigator. Doing all that other stuff AND deleting "Recovered Resources" is what worked for me. Along the way, I deleted and added back the problem files, added them to Target Membership in the File Inspector, rebuilt the Package Cache (right click on Package Dependencies), and waved a dead chicken over the keyboard. I think deleting "Recovered Resources" was the key.

Tinkle answered 14/11, 2022 at 21:51 Comment(0)

D

-1

Go to File --> Workspace Setting --> Change "Build System" to "Legacy Build System" from "New Build System

Recommended topics

Hot tags