Summary of Issues: MDCrashReportTool, Backup, Sync, Preparing to Sync

Summary of Issues: MDCrashReportTool, Backup, Sync, Preparing to Sync


Disclaimer: This summarization is sourced from multiple community threads. By no means am I claiming this summary is all encompassing nor am I claiming to be a subject matter expert. Not everyone is having the same experience. Let's see how it goes anyway. Hopefully you will find it helpful.


What is the issue?

Data sync error details are collected and reported to Apple by an automated tool (MDCrashReportTool) which is known to sometimes stall, never giving control back to the parent process.

Is this a new issue?

No. MDCrashReportTool has been in existence since at least July, 2008 and the "stalling issue" has existed since 2009 and perhaps prior.


Is Apple actively working to resolve?

Only Apple can answer the question. Apple has acknowledged awareness of the issue but defects unresolved for so long are not likely to be resolved anytime soon, if at all.


Does this issue impact both Apple and Windows users?

Yes. Sync processing can be initiated via the Finder app for Apple users with current macOS software or from iTunes for Windows users and Apple users on older versions of macOS.


Are all users having this issue?

No. Devices synched using iCloud do not seem to be experiencing the issue. Users that sync data between devices initiated from the Finder or iTunes apps may experience the stalling issue.


Is this an Apple Watch issue?

No. Users both with and without an Apple Watch report experiencing a sync stalling issue so this is not exclusive to Apple Watch users.


Is this a cable issue?

No. Regardless of whether the device is wired or wirelessly connected, the sync process may fail/stall. One difference is a wire connected device that has failed to sync, if disconnected and reconnected while the "automatic sync when connected" setting is on will immediately attempt to continue where it last failed. With this setting turned off, and the setting for "show this iPhone when on WiFi" is set to "on", a sync will only begin if clicking the SYNC button and it will start fresh instead of where it last stalled. This will not guarantee a successful sync but does illustrate this is not a cable issue.


A stalled sync may complete after a force quit of MDCrashReportTool. How?

MAC computer: open the Activity Monitor found in the Applications/Utilities folder. In the app, search for MDCrashReportingTool. Highlight the process name and click the ⓧ icon. Select Force Quit from the popup menu.

Win computer: start the Task Manager. In Details, find NDCrashReportTool (may need to expand iTunes to see it). End NDCrashReportTool.


Is force quitting MDCrashReportTool a recent discovery?

No. Using this method has been around since release iOS 5. Also, there is a January, 2008 thread in the Apple Community (Title: Can't sync music) that mentions MDCrashReportTool.


Is force quitting MDCrashReportTool a fix or solution?

No. While this will allow the Sync to complete, no software is modified to correct the root cause. Until then, for every stall, a force quit is need to complete the sync.


Is there a way to automate the process so sync does not stall?

Yes. One way is to rename the MDCrashReportTool file extension so the process cannot be executed. Alternately, one might replace the file with a same named file that does nothing but return control to the parent process. Instructions are not included here as steps are dependent on the operating system and for iTunes users, whether the app is installed locally.


Is there a negative result in causing MDCrashReportTool to quit?

Yes/No. MDCrashReportTool automates error reporting. Prior to this tool development, the user would have to manually find, extract and publish error details to file a ticket with Apple. Quitting the tool puts error reporting responsibility on the user, likely resulting in fewer reports going to Apple.


Note: Running a "backup" is a five step process of which step 3 of 5 is "Preparing to Sync". A force quit of MDCrashReportTool will cause step 3 to complete in a flash but in testing, it appears steps 4 and 5 do not run. This leaves an open question of whether the resulting backup is complete. Apple may need to provide an answer.


What has not been addressed above:

(1) Effect of modifying settings for what is included in a sync

(2) How to identify file(s) the sync could not process, if any

(3) Does cancelling MDCrashReportTool leave behind log files that are never deleted?

(4) Instructions for renaming MDCrashReportTool

(5) For a stalled SYNC, any data not moved from iPhone to computer and/or computer to iPhone

(6) For BACKUP, the data result restoring an iPhone from a backup that previously stalled


-R.

Posted on Dec 20, 2023 12:56 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 31, 2023 8:32 AM

TerPri wrote:

I am able to navigateto MDCrashReportTool but am unable to rename it. Can anyone provide directions on how to accomplish this?
thanks

TerPri, if you are trying to rename the tool via the Activity Monitor, that is definitely not the way to do so.


You will need to navigate to the file using Finder (assuming you are on a Mac) as follows:


/Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileDeviceHelper.app


Right click on AppleMobileDeviceHelper.app and select "Show Package Contents" followed by /Contents/Resources/MDCrashReportTool


From there you should be able to rename the tool if you are signed into your computer with admin rights.


Good luck

-R.

Similar questions

82 replies

Jan 28, 2024 11:02 AM in response to Northern-Survivor

Northern-Survivor wrote:

I suspect we’re seeing the infinite data set problem. That is, we have standard software - the operating systems and applications; yes they’re customisable to some extent by “settings”, but we’re all using the same software for any given version. But we all use it differently, on different hardware, each users data (emails, music, photos, files etc, etc ) is unique to them. .

Northern-Survivor,


I believe it is also the fallacy of "no bug software". It really does not exist.


-R.

Feb 2, 2024 1:58 PM in response to Ron_NJ

It's absolutely disgraceful that they aren't fixed this issue. It leaves only the obvious conclusion that the only reason this has not been fixed is because Apple refuses to. It's that simple. It is widespread enough they are clearly aware of it, and ave fixed issues with a smaller impact than this. They do not want you syncing music from your computer to your phone. They want you paying a subscription for Apple Music and for larger iCloud storage. If you aren't, this is how they show you that they are content to allow users affected by this to deal with an obnoxious flaw. In fact, it kinda looks like this issue is a deliberate attempt by apple to hamstring devices for that purpose. It's common enough that it is not affected "a small amount of users", but because it isn't everyone, they can plausibly claim that it isn't deliberate. But it is, without a doubt, infuriating and unacceptable that it hasn't been addressed after all these years.

Feb 10, 2024 5:07 AM in response to spawnster

spawnster wrote:

Somehow someway this issue has been fixed. I’m now able to sync without issue.
Unfortunately today (February 9) was a new update and my Ticketmaster passes are now disabled…again. Last time this happened I reset the network settings and all was good. Like you said short-lived. This no longer works. Does this go back to the syncing problem?

Essentially what you are saying is that the issue you raised on January 27th about Ticketmaster passes being disabled has not been resolved by Apple as of February 9th, even though they have acknowledged this is a known issue.


Can you identify where your tickets are located (PC, Mac, tablet, watch, email, wallet)? While hard to say definitively this is related to sync, it may be.


Wouldn't it be great if Ticketmaster knew about the issue and put some pressure on Apple to resolve as it could impact Ticketmaster's business/customers?


-R.

Feb 12, 2024 1:41 AM in response to Ron_NJ

With the one hand Apple gives, with the other they take away. The sync issue had been fixed prior to the update to 17.3.1. Now it’s back to getting stuck on step 3 of 4.

I’m sure it’s not just me that sees each time there’s a new update to the iOS, something goes wrong.

Either it’s this or more recently Ticketmaster concert tickets being disabled in Apple Wallet.

I’d really like to know what’s going on at HQ. I’ve been using an iPhone since 2009 and have never seen issues like this before. Not on such a regular basis.

Mar 31, 2024 12:05 AM in response to rsworden

Hello! I was able to force quit MDCrashReportTool before, but now I cannot find it in the Activity Monitor. I tried to follow your advice, but I cannot rename the icon even if I am the administrator. This photo bug is a nightmare; I do not understand why Apple does not fix it. Transferring pictures and synching the phone have always been big sources of stress. EVERY TIME there is a problem. Please, please...what can I do!?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Summary of Issues: MDCrashReportTool, Backup, Sync, Preparing to Sync

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.