“tmp” couldn't be removed because you don't have permission to access it

Question

While trying to invoke simulator on macincloud server, I am getting the following error.

Steps tried by me:
1) Searched for "tmp" directories on my mac machine, but do not see any.
2) Tried to reset simulator, but after the confirmation screen (which asks whether or not to reset simulator), it throws the same error as mentioned above.

The permissions on the Xcode directory is as follows:

From the Activity Monitor I searched for the processes related to simulator and using the logs I could figure out the location of "tmp" folder, trying to delete which simulator is throwing the error. When I am trying to remove the folder manually, I get below error:

So which means root user is required to delete the "tmp" directory. Since I am using a non-root user to invoke the simulator, what can I do to overcome this issue?

EDIT: I have elevated the permissions for my account recursively on my home and I have the following permissions:

After changing the permissions when I try to delete contents of tmp directory I get this error:

So I think there is something wrong with the permissions that I have provided on the folders/files under my home directory.

Answer 1

I am describing a solution here - basically you have to remove the defunct simulator in ~/Library/Developer/CoreSimulator/Devices and recreate it.

The fine snapshot by Felix Krause - which I also explain how to use in this article - helps you to completely reset your simulators to a pristine state.

Answer 2

I have this issue in iPhone 6 Simulator (iOS 9.0). Please check whether all the simulators having this issue or particular simulator.

I have re created the iPhone 6 simulator in the Xcode -> Window -> Organiser. The newly created simulator works fine.

Answer 3

Just incase it helps others, I think I managed to get in to this state by stopping the build when stopped at a breakpoint (whilst it was paused on the breakpoint I changed my CoreData data model which may have played a part). It's the first time it's happened to me, I just closed the simulator fully and re-run the code (obviously crashed due to the model change as I'm not merging), after it crashed it allowed me to reset the simulator so maybe it locks up during model changes? Just a guess though but thought I would add the steps it took me to create it as it literally just happened.