Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fa8bad9a6f0>

Question

I'm working on a project for iOS and I'm doing the programming with Visual Studios and it connects to a mac server using Xamarin. I recently tried to add more views to the storyboard and an additional class. When I tried to build the code, I received this error. http://pastebin.com/Ub5s89aa This is what the output from the console. http://pastebin.com/fhWDy2cJ

I don't know what this error means and when I tried to look up any part of the error, nothing helped. I cleaned my builded and tried to rebuild, and I also closed Visual Studios and reopen it to see if that help, but it didn't. Has anyone else had this problem before?

Solution 1

Restarting the CoreSimulatorService solved the issue on my machine.

sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService

Solution 2

I had the same problem after I upgrade my Xcode to version 10.3.

I just restart my Mac and problem solved!

---

Hope this would work with you too :)

Solution 3

Mine happened when updating to Xcode 10.3

X-code helper didn't get the permission to control the computer.

This is what i did to solve the problem

System Preference > Security&Privacy > privacy tab > accessibility

give permission for 'Xcode Helper'

Restart X-code and kill all simulators like @riik stated

sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService

Solution 4

This issue is with xcode update 10.3 and mixpannel is gives this as build error

Steps to fix.

Open terminal and paste this

sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService

Clean Xcode and build. Thats all

Solution 5

After having a google I found a similar question here and here, summary of the some of the answers in that question:

• Make sure you are running the latest version of Xcode and you dont have a beta installed.
• Close Xcode and then opened up Activity Monitor. Terminate any Ibtool processes running and restart Xcode.
• Delete any custom color pickers you have installed in for Xcode, close the Xcode and relaunch
• Try recreating any nibs you may have changed.

summary from the Xamarin Forums link:

Uninstall Xamarin studio, Xcode
Delete /Libraries/Developer and ~/Libraries/Developer folders
Reboot
Reinstall Xcode, Xamarin studio

If none of these work could you check in the Console.app for any errors when building.

Hope this helps.

View more solutions

Comments

[BradzTech]

Was there something you changed in the code that caused this problem to start happening, or have you never been able to build the code?

[Adam Lietzau]

I was able to build the code before. I recently added two table view controllers and a class. When I removed both, it did not fix the issue.

[BradzTech]

Try cleaning your project, deleting derived data, and ensure there are no unconnected IBOutlets. Also make sure you didn't accidentally change anything in your app's build settings; the error you posted seems to have something to do with architecture inconsistency.

[Adam Lietzau]

I wasn't able to find out what the exact issue was. I talked to my professor and he things it might have been an unconnected IBOutlet like you mention. I rolled back my project to before I made the changes and it works so far. I will make sure to be testing my builds before I make major edits like I did and I will post if the error comes up again.

[Vladyslav Zavalykhatko]

You are fine with just running the command @riik proposed. No need to restart

[Sunil Targe]

@VladyslavZavalykhatko Thought running command will reset all my simulator and then hard to reinstall all again. So choose restart and it works!

[Wayne Henderson]

Same experience: Error popped up after update to Xcode 10.3. Restart made the error go away. My MacBook restarts in under 1 minute, so this fix is about as simple as can be.

[Joe Maher]

Standard xcode update breaking random things with no explanation

[Sunil Targe]

@JoeMaher Yes actually

[Enea Dume]

I had the same problem after I upgrade my Xcode to version: 10.3. Open terminal and run: sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Then do a Clean Build folder and the error is gone.

[Scott Gardner]

This happened to me with the latest Xcode 10.3 (10G8) release, and this answer resolved the issue. Thanks!

[auspicious99]

I just "upgraded" to Xcode 10.3 too, will try the restart.

[auspicious99]

Yes, after restarting, I didn't encounter the problem again.

[Sam Grant]

Yep, worked for me... had this issue after upgrading to the latest XCode (10.13 10G8) & Mojave (10.14.6).

[Mike]

Worked for me too! Got the same error after upgrading XCode from 10.2 to 10.3 (10G8), using macOS Mojave 10.14.5 (18F132)

[realtebo]

I can confirm it worked under quasar dev mode cordova on Max 10.14.6 and Xocde 10.13. Even in my case the problem happened after upgrading Xcode

[randomcontrol]

I think that saved a lot of developers a lot of headache! Thanks for sharing that information with us!

[Mattia Ducci]

Yeah! Worked for me!

[Jonathan Kaufman]

riik you're a god. was building from Unity and thought for sure I was in for a long night (the interaction can be quirky between Unity/Xcode). this was an immediate fix. fastest solution I've had in 7 years on stackoverflow. well done.

[CyberMew]

Went from Xcode 10.1 to 10.3 and got this same error as well, thought it was something to do with React Native code or the macOS version (10.14.5). Solution works.

[slobodans]

I had same problem after setting up Flutter for iOS. This solution fixed problem. Thank you.

[Cheung]

This issue happen after I upgrade the Xcode version, the resolution is works!

[Lucy]

Wow, thanks for this answer! It solved the problem! I also had upgraded to 10.3 when it happened.

[dragonfire]

For me I also had to restart XCode. Just a note for others

[Dmytro Rostopira]

I've ignored this answer, because don't use simulator at all. However apparently it still can break my build. I flipping love XCode

[JRV]

I have experienced the same issue since upgrading to Xcode 12.5: Restarting Mac and restarting CoreSimulatorService did not work, but reinstalling Command Line Tools as described in the answer worked

[Carlos De la Mora]

Xcode 13.4, this worked for me, the other answers did not.