Views: 46
Thank you for reading this post, don't forget to subscribe!
This post is dedicated to anyone who develops a Mac, tvOS, or iOS app using Xcode. Every once in a while, we come across those errors that seem to come out from nowhere. Especially those who tend to come up right in the middle of a major project that has to be tested on an actual device.
The other day, I ran into the said error (see included graphic). I than restarted Xcode (which didn’t work), rebooted my Mac, and my iPhone, to which none of these worked.
I then went to Google and typed the above error into the search engine, and came across this post from our saving grace website called stackoverflow.com. After reading some of the posts, I came across the below:
A simple phone restart will fix it
I have had to come back to this SO question twice in the past couple weeks. First time, I did have to update my Xcode and iOS versions, which fixed the issue. Now, the issue has returned, but there are no updates. I tried disconnecting and reconnecting my phone from my laptop, but to no avail.
What fixed it the second time was merely restarting my phone. I am curious if that would have fixed it the first time too, without needing to have updated.
I know this is just echoing the other answers here, but at the very least, I would recommend just starting with a simple phone restart and seeing if that fixes your problem. Here is the specific screenshot that I encountered, in case yours is the same (pro tip: you can open up the “Devices and Simulators” window by going to Window -> Devices and Simulators
shift-command-2
).
So, now you know. 🙂