Final Cut Pro "error -536870186" - won't export/share file

How large is the drive and how much free space?

Have you tried deleting the render cache? Maybe it's a corrupt cache file. Select the library in the browser, choose File->Delete Generated Library Files... Choose All Render files. Manage render files in Final Cut Pro for Mac - Apple Support 

That number looks familiar to me.

Are any of the drives you're using formatted any other way besides APFS or HFS+?

If yes, try exporting to and/or from an APFS or HFS+ drive.

If no, then I'd try a safe boot (and then a reboot)

Start up your Mac in safe mode - Apple Support

As a test, I'd also disconnect any and all external drives, devices, headphones, etc... you don't actually need for the export.

If you can, you could search for "536870186" (without quotes) in the logs.

I was able to fix this by deleting a section of video that had a fragmented/disrupted frame. This must have happened while filming and while the video looked almost normal there was a small glitch during playback, deleting that section allowed me to export the rest of the video. Hope this helps!

Delete preferences, delete render files, and try again.

The error does not mention a specific frame, does it?

Hello. I also have the same problem. It came out of nowhere. I was exporting fine, untill a certain momment decided to export in Apple Pro Res. It failed to export in 2 different external disks ( one ssd, other hdd) and failed also to export to the internal Mac studio disk. Nothing works.

Mike Rydell, where you able to solve your problem? Thank you

Hugo_FM81 wrote:

Nothing works.

Respondents have provided confirmation items. Do you meet all the conditions? Please respond with the items you have fulfilled and the questions below.

--

Q1: Will I get an error if I change the format from "Video and Audio" to "Computer"?

Q2: Will an error occur if I change the video codec from “ProRes” to “H.264”?

you would think that an error that apple LITERALLY has a code for would at least try to explain wtf is actually wrong. but of course they have us in this forum guessing what could be wrong. this is one of those errors that just simple makes no sense. There's no cause or reason. it's just pure technological spite. But what else is new with apple. They love having their customers stress tf out wondering how to fix an issue when they could easily give us an explanation.