I just upgraded Xcode 8.0 from beta 4 to beta 6 and I am getting this message " unable to read from device " when trying to build the app on my device. Any ideas what the problem could be?
-
1Restarted device helped me. – Kamleshwar Aug 16 '16 at 23:02
-
Yep, just restarting the device was enough for me, too. Glad I didn't go to the hassle of removing `iOS DeviceSupport` folder which I'm sure helps sometimes but apparently would be a waste of time and hassle at many other times. – PeterT Aug 20 '17 at 09:37
-
But when restart the device it works only once for me. Every time I try to use this I have to restart phone and this is not feasible. – Hope Sep 04 '17 at 07:31
15 Answers
This is the error when the symbols are missing. Usually you get this error when your device has higher version than the Xcode such as iOS 10 vs Xcode 7.3 In this case Xcode 8 beta 6 failed to copy iOS 10 beta 6 symbols from the device.
- Open Devices in Xcode
- Select your device. It should have an unexpected error message
- Delete "~/Library/Developer/Xcode/iOS DeviceSupport" directory
- Unplug your device
- Restart your device
- Plug back your device
- Xcode should start copying the symbol files immediately

- 21,461
- 5
- 90
- 86
-
2This *almost* worked for me — step 4 wasn't enough, I had to restart my iOS device and quit and restart Xcode to get it to start reading the symbols, but then it did so. (Initially the Devices window showed "unable to read from device", then "unexpected" as you describe above, until I restarted Xcode.) – Nicholas Riley Aug 25 '16 at 15:21
-
@NicholasRiley probably it's more robust that way, I updated the answer. Thanks – Tibidabo Aug 26 '16 at 03:09
-
This also worked for me, after closing Xcode while unplugging and hard restarting the iOS device, and opening Xcode after having plugged in the device again. – mbo42 Aug 29 '16 at 04:16
-
5Thank you for this - I was clueless! However, why delete the whole symbols folder? it took me hours to build it for all the devices I'm using. You only need to remove `rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/10*` – ishahak Aug 31 '16 at 12:04
-
1I had the "Unable to Read Device" error. This worked for me, but had to repeat the steps and on 4, I left the device plugged in. When device restarted I got the "Unexpected Error". I restarted xcode and it began processing symbols. – johnrechd Sep 01 '16 at 16:07
-
I got it to work. Try restarting your device.
If not, delete the contents of /Users/yourusername/Library/Developer/Xcode/iOS DeviceSupport, plug it into Xcode again and let it process symbol files.

- 499
- 4
- 14
-
1I actually called apple and they told me to do that. Any idea regarding webkit-playsinline="webkit-playsinline" my video keeps opening fullscreen – Michel Arteta Aug 16 '16 at 02:53
-
2its also worth mentioning that while a new folder is created in that directory when I plug my device in, that folder never contains anything – YichenBman Aug 16 '16 at 16:31
-
-
@rmvz3 to be honest, this has happened to me too. I still couldn't find a definitive solution. I keep trying a random sequence of deleting that path, restarting macos, restarting ios and close & open xcode-beta. It will work sometime ☹️ – diegotrevisan Aug 27 '16 at 19:59
-
@diegotrevisan In fact. My case seems to be even worst because I'm facing this problem with the official Xcode 7, not beta version :( – rmvz3 Aug 28 '16 at 16:28
-
-
@diegotrevisan Yes. I'm running iOS10 and Sierra but I haven't had any problems until beta7. – rmvz3 Aug 28 '16 at 20:49
-
@rmvz3 Yes I'm facing it with Xcode 7 too. I meant you might have to open Xcode 8 to fix this issue (to let it process symbols). – diegotrevisan Aug 28 '16 at 21:32
-
I found myself with the same issue, also my iOS > Settings > Developer: Turned out to be blank.
Solution
On iOS device go:
- Settings > General > Reset > Reset Network settings
- Device will reboot ( and you will lose wifi passwords etc )
- Start Xcode 8 ( beta 6 ) and plug your device in.
If this alone not work try following
- Unplug your device.
- Reboot your Mac
- Download Xcode 8 beta 6 and put it in applications folder.
- Delete content of: /Users/User/Library/Developer/Xcode/iOS DeviceSupport.
- Performance the steps above to Reset Network settings on iOS 10 device.
- When iOS device starts up plug it into your Mac, Accept it as trusted device
- Start Xcode 8 beta 6.
Hopefully this will work for everyone else, the list above include all the most common fixes.

- 3,562
- 6
- 30
- 46
-
It helped me only after MAC reboot. Otherwise it was all the same. Thank you a lot. – Miroslav Sep 14 '16 at 12:06
- Update Xcode to Xcode 8 beta 6
- And Reset Network on your iPhone (Settings > General > Reset > Reset Network settings).
That worked for me.

- 137
- 5
-
Cleared all my network settings including those connected to my iCloud. Keep that in mind before trying this out – Yannick Aug 22 '16 at 14:40
- Update Xcode to Xcode 8 beta 6 (https://developer.apple.com/download/)
- Reset your iPhone with the Home/Power button combo
I didn't need to do the Reset Network step for the phone.

- 83
- 6
-
+1 for `Reset your iPhone with the Home/Power button combo` This indeed triggered Xcode to process symbol files. (Note: Unplug your device while it's rebooting otherwise it mind end up in an unknown error in Xcode - Window - Device.) – DevAndArtist Aug 30 '16 at 09:31
Few hours back i got same issue. Following below steps fixed my issue.
- Restart Mac
- Restart iOS device
- Open xcode beta
- Open devices window from "window->Devices" menu
- Click on iPad and wait until "load symbols" progress indicator finishes.
It took me 10mins to load symbols, then Xcode detected device. And i had to restart twice iOS device and once Mac.
In case, if you see error after step5, hard restart iOS device (press home button and sleep button at a time and wait for apple logo to appear) and try same from step1.
My configuration: Mac(10.11.6), iPad (build version: 10.0_14A5341a), XCode 8.0 beta 6
Hope this helps :)

- 39
- 2
-
In my case it helped... restarted everything and deleted the old symbol files – Nico S. Aug 17 '16 at 16:26
Just restart your device
It's work for me... May be it's work for you also...

- 2,572
- 26
- 41
For me, changing the development target to 9 and then back to 10 worked.

- 159
- 1
- 10
Had same issue here. Fixed it by reseting the device (Power Button + Home Button) and replacing the lightning with an original one (apparently I was using one of those replicas) .

- 2,437
- 4
- 27
- 36
Xcode 10 re-pair device fix problems for me.
- Open devices: select menu Xcode > Window > Devices and Simulators ⌘+⇧+2
- Inside window "Devices and Simulators":
- Select your device in left column
- Right click on device to open list menu
- Select list menu "Unpair Device"
- Device will show "Trust dialog" > choose trust. If dialog not shown, on device open system Settings > Developer > Clear Trusted Computers

- 799
- 12
- 17
I was facing this issue on XCode 8 Beta 4. Updating XCode to XCode 8 Beta 6 resolved the issue.
I read somewhere that "Settings->General->Reset->Reset All Settings" resolves this issue. It did not help me but I had done it anyway. Not sure if Settings need to be reset along with updating XCode.

- 575
- 4
- 18
None of the above solutions worked for me. Turns out it wont download symbol files if you are using the GM for tvOS 10. I removed the provisioning profile for the GM and it worked like a charm.
Hope this was helpful to someone.

- 860
- 1
- 10
- 21
I tried the all the steps above, and reboot, restart both phone and my mac book, none of them works. I end up to download Xcode Version 8.1 (8T61a) and it works. My phone's os version is iOS 10.1 In xcode 8.1, my swift files have to have some minor syntax changes to be build.

- 489
- 5
- 5
my two cents: I can confirm same trivial fix for Version 9.2 (9C40b)and highSierra / OS 11.2.5 (15D60)
I got the same error, but after restarting OSX it did work.

- 10,876
- 3
- 61
- 48
I had the same problem with 14A5341a. As several reboots did not lead to any improvements, I dug deeper and found that the issue appeared as soon as I started tracking my device via iCloud. As soon as I switched tracking off, everything worked as expected again.

- 1
- 1