Iphone is busy processing symbol files

iPhone is busy: Making Apple Watch ready for development

Since I upgraded to iOS 15, watchOS 8 and Xcode 13, after I turned off and on my Mac, every first time I want to launch an app from Xcode to my iPhone appear this message (even if I’m not developing for watchOS):

The Mac stays stuck on it for at least 20 minutes.

The only solution I found (until now) is to switch off WiFi on my Watch.

Is there a better solution?

Answers

You might have better luck asking this question over in Apple Support Communities run by Apple Support.

Did you try to reboot the watch ?

If that’s not enough, try to unpair the watch from iPhone and pair it again.

Toggling Aeroplane mode also works

Airplane — not working. Thousand time this ******** appear.

Having the same issue on Xcode 13.0, iOS 14.7.1 and WatchOS 7.1, also in trying to debug an iOS app (i.e. I’m not developing for WatchOS). I’ve restarted the computer, watch and phone, and unpaired / re-paired the phone from Xcode’s devices, but can’t get it to work consistently (I get stuck on «Making Apple Watch ready for development» maybe every other or every third time I try to launch the app).

Turning the watch off entirely does the trick (as I imagine airplane mode would too), but I’d like for my watch to work as well 😕

Facing this issue since Xcode 13 betas. Disabling Bluetooth in the iPhone temporarily fixes the issue for me.

With the Control Center Bluetooth icon in grey, no need to fully disable it in the Settings app.

I had the same problem, but iOS 15.0.2 / watchOS 8.0.1 no longer causes the problem.

I still have this issue in iOS 15.2 and watchOS 8.2. The issue was never gone.

This issue is driving me nuts. And for me it happens literally every time I plug in my iPhone. Unplug, plug it back in, wait 5 minutes for Xcode to make the watch ready for development. Which then usually (but not always) fails by the way! Plug it back in, and you’re just stuck waiting for 5 minutes yet again.

When it fails, I get this error:

Unable to prepare iPhone for development Could not locate the device support files.

But building an app to my iPhone still works 🤷‍♂️

Источник

XCode stuck with «Copying symbol files»

After updating to the latest version (6.1 b2) Xcode does not compile and run projects on the device anymore and shows «Copying symbol files» for hours. Any ideas or possible workarounds for this problems?

11 Answers 11

Try to use another cable or USB port — Other usb port fixed it for me and got the idea while finding this twitter post: [Tweet Gone]

I encountered the same problem. «Rebooting my iPhone» worked for me.

1. Clean Project
2. Option + Product -> Clean Build Folder
3. Remove this folder Library/Developer/Xcode/DerivedData/ModuleCache
4. Find your project folder in Library/Developer/Xcode/DerivedData/ and remove
5. Restart Xcode

I just spent the last several hours troubleshooting this issue on my device. I am running a virtual version of Mavericks on VBox. For me, the problem was resolved by installing Oracle VM Virtualbox Extension Pack. There was a problem with VBox fully recognizing the USB. It would recognize in iTunes, but not in XCode. This may be helpful for anyone running XCode on a virtual machine

/Library/Developer/Xcode/iOS DeviceSupport for your device folder, it should go over 1GB (took about 10 min). Previously it was stuck at 300Kb.

Also you can try just to reboot your device — helps for me.

In my case, «Rebooting Xcode» & ensuring my iPhone was unlocked did the trick.

It appears that my Symbols file download began previously (as the Symbols directory for iOS 7.1.2 was in the expected location in

/Library/Developer/Xcode/iOS DeviceSupport/), but did not complete, & thus sometimes was «sticking» and other times completing but showing my iPhone as unavailable.

When I restarted Xcode, I ensured that I already had the iPhone unlocked & then instead of just getting the «Copying symbol files» message, I also got a «Processing symbol files» message, after which my iPhone was available to run the app.

Источник

Fixing Xcode 9 issue: «iPhone is busy: Preparing debugger support for iPhone»

I’m looking for more information on the message below. Xcode 9 seems to be hanging for a couple minutes already.

How can I tell Xcode 9 to quickly recognize my previously used device updated to iOS 11?

.Alex’s iPhone is busy: Preparing debugger support for .Alex’s iPhone
Xcode will continue when .Alex’s iPhone is finished.

36 Answers 36

There are multiple solutions for this:

Solution 1: Patiently wait for 10 to 15 minutes. Have a tea or roam around 😉

Solution 2: Disconnect device from the system. Restart both iPhone and Xcode and then rebuild again.

Solution 3:

Go to Windows → Devices and Simulators (Shortcut key: cmd+shift+2)

You’ll see iPhone device connected to system with message

iPhone is busy: Preparing debugger support for iPhone

Click on plus button (+) present in bottom-left corner.

This will show the device connected to system. Click on Next button.

Thereafter you’ll see ‘device setup was successful’. Click on Done button.

Solution 3 worked for me!

Solution 4:

Unpair your device and then pair it again. Thereafter follow Step 3.

I clicked ‘Cancel Running’, opened the Devices list, unpaired my iPhone, removed my USB cable and reconnected it, paired the iPhone, and then was asked on my iPhone to enter my passcode («pin code»). Did this and then was finally able to pair my phone correctly.

Wait a few minutes. The application will start automatically

Restarting Xcode worked for me (quit and start again).

What didn’t work for me:

• waiting for an hour on one device
• waiting for an hour on another device
• restarting devices
• unpairing/pairing devices

It turns out XCode opens device manager window beneath it and waits for you to hit the next button. Switch to that window, hit next and you get the progress bar for the process to show up.

In my case, iTunes was open, so

2 — access you phone

3 — click to disconnect your phone

Now the device is ready on XCode

below solution worked for me, follow steps to resolve your issue:

Step 1: Cancel Running

Step 2 : open Window menu and select Devices and Simulators

Step 3 : Unpair the iPhone

Step 4 : Removed iPhone USB cable and reconnect to the system

Step 5 : Pair the iPhone when you connect then you will be asked to Trust or Don’t Allow, Please click Truct on your iPhone and enter your passcode (Pin Code)

Note : I performed all the above steps they worked for me. The issue of my device debugger gone.

Below is the Screenshot of Devices and Simulators Menu

I unplugged my cable and saw this. After it reached the end I was able to run it no problems.

You don’t have to unplug to see this; just hit cancel and you will see its progress.

1. Click on Window menu
2. Select Device and Simulators
3. Select your device
4. Click on + button at bottom left corner
5. Click Next
6. Click Done

I found deleting the app from the device and re-installing with Xcode solved this issue.

I realised I had less than 100 MBs of free space on my disc. Freeing up disk space solved the issue for me!

• Open Window -> Devices and Simulators
• Unpair iPhone on the side list
• Unplug and plug again the USB cable
• Press Trust in the prompt message in the device!
• Then it should work! It worked for me

I have been using my iPhone X to debug via Network and suddenly had this problem.

Disable «Connect via network» and try again with USB. This trick worked for me.

When you plug a New device which is having iOS 11, Xcode 9 will Prepare Debugger Support for that device, At this time you should Wait to complete it.

Then run the project in that device it will run smoothly.

If you didn’t keep patience while creating Debugger Support then it will throw the error mentioned in the question.

The Best way:

1. Disconnect the Iphone.
2. Clean xcode by command+ shift + k or by going to Product -> Clean

rebooted iPhone, closed all other open applications and unlocked phone worked

I had the same problem many times, these things worked for me:

• restarting my phone + xCode.
• checking that both your Mac and your iPhone are connected to the same Network.( has a high potential ).
• repairing my phone.

Tried all the «speedrun» tips up till 2019-11-24 without luck. The wait seemed inevitable but incredibly long in my case:

with a freshly upgraded iOS version.

I then found this comment on reddit which makes the most sense:

This is required when you connect a device with an iOS version that the respective computer’s Xcode didn’t see before. It saves them in /Users/username/Library/Developer/Xcode/iOS DeviceSupport and it does take a while. Don’t restart Xcode as it will not help you, just wait for it to finish.

It takes quite some time because these debugger support files occupy a lot of space (29 GB for me), though you can safely delete any version from there, and if you connect a device with that version again, it will re-save it from scratch.

So if you just upgraded your iOS, then the «from scratch» part could take longer than usual, also depending on your network condition. In my case, it is definitely much much longer than the «10-15min» other people claimed. I measure it by hours.

A lot of tricks seem to have worked but they neglect the fact that time goes on as you try things while Xcode keeps working on the setup in the background, and quite possibly resumes its job whenever you do a restart/reboot cycle.

This led me to noticing that my Xcode version is just one step behind the iOS point release. After upgrading my Xcode, it worked.

But it took longer because I removed the iOS DeviceSupport folder by following a tip!

So here are my suggestions:

• Check your Xcode version down to the minor version to make sure it should actually support the iOS version.
• Check your Mac’s free disk space to make room for newly generated device support content under

/Library/Developer/Xcode/iOS DeviceSupport as this tip suggested.

Check if you have connected your device to a fast-enough USB port, as this tip suggests.

Wait till Xcode finishes «preparing for debugging».

If it doesn’t finish in a few seconds or minutes, keep waiting.

DO NOT remove any folder as some tips may suggest. Removal would simply make you wait longer!

Источник

Iphone is busy processing symbol files

Share iOS system symbol files copied from iOS DeviceSupport folder. Useful for symbolicating iOS crash reports.

When I get new symbol file, i will add it into the google drive sharing folder, and update the collected-symbol-files.md. You can follow this repository to get the latest update.

What’s the use of system symbol files

It’s for symbolicating those system frameworks in your iOS crash report.

When you get a crash report like this:

The callstack didn’t catch your app’s code, it only has code from system frameworks. So you need to symbolicate these system code.

Here is the symbolicated report, those were changed into specific method names:

We can make out that the problem was caused by UISearchDisplayController ‘s delegate . It’s assign . This crash happened when tap search bar while poping the viewController.

The problem of symbolicating system frameworks

You may find out that you can’t always symbolicate those system code. There’re several problems:

• If you want to symbolicate system frameworks in your crash report, you need the corresponding system symbols, matching the OS Version and CPU architecture.
• Most system symbols can only be got from physical iOS devices. Apple never offer a website to download these symbols.
• You can download old versions of Xcode and pull out the SDK image you need. Usually the symbols are part of the latest Xcode release, but Apple doesn’t always provide Xcode updates when an iOS version only contains bug-fixes but no API changes. And since Apple replace system framework with tbd files after Xcode7, this trick doesn’t work any more. Read this for more details: Xcode software image for user iOS in order to symbolicate iOS calls, Missing iOS symbols at “

/Library/Developer/Xcode/iOS DeviceSupport”. (Update: Actually, since Xcode 6, there is no real device SDK. So you can only get SDKs before iOS 7 from Xcode.)

When you first connect a new iOS device to Xcode, Xcode will show a loading message: Processing symbol files (after Xcode 9, it’s Preparing debugger support for Device ). It’s copying system symbol files from device to your Mac’s path:

That means you need a corresponding device if you want to symbolicate a crash report. There are 132 versions from 7.0 (11A465) to 10.2.1 (14D27) (most OS version contains three different type: arm64 , armv7s , armv7 . A arm64 device contains both arm64 and armv7s ). That’s obviously very difficult to collect them all.

That’s the meaning of this repository, to share these system symbols.

update: Since iOS 10, iOS firmware are not encrypted, so we can get symbols from firmware now.

When you need to symbolicate a crash report, check the Code Type and OS Version section. Such as: Code Type: ARM-64 OS Version: iOS 10.2 (14C82) . That means you need arm64 version symbols of 10.2 (14C82) system.

Find the package in my sharing folder and extract it to

/Library/Developer/Xcode/iOS DeviceSupport . (Check the file’s name and path, it should be

/Library/Developer/Xcode/iOS DeviceSupport/10.2 (14C82)/Symbols ).

Use Xcode’s symbolicatecrash tool to symbolicate your crash report. This tool will search system symbols in the iOS DeviceSupport path automatically. Read this to learn how to use symbolicatecrash : Symbolicating an iOS Crash Report.

Extract Symbols from Firmware

If the symbols you need is not in the list, you can get from firmware by yourself.

We can almost get all systems’ symbols from firmwares now. And after iOS 10, firmwares are not encrypted any more. You can also get symbols of beta firmwares.

How to extract symbols from firmware:

1. Download the ipsw firmware (not OTA files), corresponding the system version you need
2. Uncompress the firmware file as zip, find the biggest dmg file(it’s the iOS system file image)
3. If the version of the firmare system is higher than iOS 10, the dmg is not encrypted. So just double click to load the image, and go to step 6
4. If the version is lower than iOS 10, you have to decrypt the dmg file with corresponding firmware key. Find key in Firmware_Keys(Under Root Filesystem section in the corresponding firmware page)
5. Decrypt dmg file with its key. You can use the dmg tool in tools: ./dmg extract encrypted.dmg decrypted.dmg -k . Then you get the decrypted.dmg , double click to load the image
6. In the image folder, go to System/Library/Caches/com.apple.dyld/ , you can get dyld_shared_cache_arm64 , dyld_shared_cache_armv7s , dyld_shared_cache_armv7 , they are the compressed system frameworks
7. Uncompress dyld_shared_cache_armxxx with dsc_extractor tool in Apple’s dyld project. I put it in tools: ./dsc_extractor ./dyld_shared_cache_armxxx ./output
8. If you need all arm64, armv7s and armv7 of frameworks, you need to extract dyld_shared_cache_arm64 , dyld_shared_cache_armv7s , dyld_shared_cache_armv7 all. Before Xcode 11, dsc_extractor will merge different architectures into same files when extracting to a same directory
9. After Xcode 11 for iOS 13.2, dsc_extractor won’t merge different architectures files. We need to merge symbols with lipo command. Try merge_symbols.sh : sh merge_symbols.sh

Then you get all system frameworks of this firmware in output folder. Put those files into a folder as a symbol file hierarchy, such as 12.0 (16A5288q)/Symbols/ , and you can use this folder to symbolicate crash report now

Thank you for reading. If this project is helpful, please give me a star 🙂

My Other Framework

I’d like to introduce ZIKRouter, a iOS dependency injection framework. ZIKRouter helps your app split into loosely-coupled components. you can see how to perfectly decouple your modules in the demo.

Источник