FCPX crashes immediately when selecting share master file

[Flavio Juliano]

Hi Joe,
I hope all is well.
I was wondering if you can help me figure out a similar problem I’m having.

FCPX crashes as well when trying to share/export a master file, be it by clicking the Share icon to the right and clicking Master File… or going through File > Share > Master File…

I have Final Cut Pro X 10.2.1 and use a Macbook Pro (mid-2012) running on Mac OS Sierra 10.12.6.
I am unable to update any of these at the moment.

So my FCPX started crashing 100% of the time when I try to share a project, no matter what size. From reading this thread and your post, I think I know what happened. I plugged my iPad Pro 2017 (2nd generation, I believe) into my my Macbook for the first time, and iTunes asked to update software so as to be able to communicate with the iPad. I said OK, and it updated.

Ever since then, FCPX has crashed while sharing.
I read the thread and searched for the anomaly in my current System > Library > PrivateFrameworks > MobileDevice.framework file… and followed the same path in my Time Machine backup from before the issue, from March. I found that the difference is there’s a new folder called XPCServices in my current system, and in Time Machine it’s not there. Screengrab here:

So my idea was to either delete that file or drag and replace the MobileDevice.framework file from Time Machine into my current system. But it won’t let me do either. I get a prompt: “XPCServices” can’t be modified or deleted because it is required by MacOS.

Do you know what I can do to start sharing again normally?

Thanks so much, and thanks anyone else who might read this and shed a light.

Be well
Flavio

[Joe Marler]

[Flavio Juliano] “So my idea was to either delete that file or drag and replace the MobileDevice.framework file from Time Machine into my current system. But it won’t let me do either. I get a prompt: “XPCServices” can’t be modified or deleted because it is required by MacOS.”

You might need to use Finder, do “Get Info” (CMD+I) on /Library/Apple/System/Library/PrivateFrameworks/Mobiledevice.framework, and set “everyone” to “read & write”, then click on the gear icon and pick “apply to enclosed items”. If that doesn’t work try it on PrivateFrameworks.

If that doesn’t work it might be caused by System Integrity Protection. There are various articles about how to disable this on older versions of MacOS, e.g: https://www.technipages.com/macos-system-integrity-protection

I have not tried this, so it’s at your own risk. Make sure you have complete backups beforehand.

In general Apple only supports the current version of MacOS and the two previous versions, so that would be Catalina, Mojave and High Sierra. You are on Sierra, so it’s unlikely this situation would ever be fixed, especially since iTunes no longer exists.

According to the OWC support chart, your 2012 MacBook Pro will support later versions of MacOS: https://eshop.macsales.com/guides/Mac_OS_X_Compatibility

[Flavio Juliano]

Hi Joe,
Thanks so much for answering here, I really appreciate your time ☺

So I FINALLY gathered the courage to go into terminal and change the security parameter to delete the ‘XPCServices’ file that was the odd-man out in the System > Library > PrivateFrameworks > MobileDevice.framework path as compared to the same path in my March Time Machine backup.

However, it didn’t work. Final Cut is still crashing when I try to export ahah.

Do you have any other idea what I can do?
Maybe replace the entire MobileDevice.framework package file with the one from March?
Maybe the report log would reveal something?

Do you think the crash report might reveal a specific file(s) that is causing this? If not, I figure I can try either:

1) Backup current state now and then restore from Time Machine March, then drag in files from current state backup to try and get things up to speed.

2) Install High Sierra (as Apple still supports it, as you said) and see what happens. And officially purchase Final Cut Pro (as I have a cracked version, that’s why I can’t update it)

Man, thanks so much for reading, if you get to this
I really appreciate any help
Have a great day!
Flavio

[Joe Marler]

[Flavio Juliano] “Do you think the crash report might reveal a specific file(s) that is causing this? If not, I figure I can try either:

1) Backup current state now and then restore from Time Machine March, then drag in files from current state backup to try and get things up to speed.

2) Install High Sierra (as Apple still supports it, as you said) and see what happens. And officially purchase Final Cut Pro (as I have a cracked version, that’s why I can’t update it)”

It is very costly from a time standpoint to debug stuff like this, plus outcome is uncertain. Often a huge amount of time is spent only to find the only alternative is upgrade.

I suggest you update to High Sierra, make a file-level back up of your FCPX libraries, then get the free evaluation version of FCPX. Due to COVID-19, Apple extended the eval period from 30 to 90 days. I think it’s still 90. That would give plenty of time to upgrade your library and test it on the latest version of FCPX, or whatever version is supported by your hardware and High Sierra. FCPX will update your old libraries to the newer version but it’s one-way only; you can’t go back. Thus the reason for the file-level backup.

Make sure you also make a file-level backup of the Final Cut Pro.app file in /Applications.

If it works or is improved, go ahead and purchase FCPX. If it doesn’t work you have a file-level backup of your libraries so can go back to the older version of FCPX. https://www.theverge.com/2020/3/26/21196321/apple-final-cut-pro-logic-pro-x-90-day-free-trial-coronavirus