iMovie 10.1.6 on El Capitan - sharing/rendering returns CompressorKit. ErrorDomain error -1 - Caused by MobileDevice.Framework provided only in X86_64 and not anymore in i386 architecture.

Hello Community, I know there are numerous posts on iMovie 10.1.XX where you can't suddenly render/share your project and end up with an error "CompressorKit. ErrorDomain error -1". I have read and tried multiple solutions found on Internet, mostly about de-installing/reinstalling iMovie, and rebooting in safe mode, then rebooting again, that did not worked for me.


I actually went to the bottom of this problem and found this was due to an iTunes update on my machine, that updated the Library MobileDevice.framework, into a newer version that is only 64bits compatible, and not anymore multi-architecture i386 and X86_64.


I wonder if Apple will continue providing moving forward this update only for the 64 bits architecture and break the old OS ?


On my machine here is how I located the trouble maker, start the utilities/console, start iMovie and attempt to render your project. After the error message, check the console, there is the offending message about the MobileDevice.framework that does not match the architecture. To solve it, get your TimeCapsule backup, locate a previous version of the library. It should be located into


/System/Library/PrivateFrameworks/MobileDevice.framework/


Which is a system protected area. So restore somewhere else, reboot in Cmd+R safe mode, and manually force replace the offending library with the previous version, restart and voilà, iMovie is happy about that compressor Library again and will proceed with the share/rendering.





MacBook Air 13", OS X 10.11

Posted on Apr 12, 2020 1:43 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 21, 2020 7:20 PM

YES!! This was exactly the solution I needed! THANK YOU!


The CompressorKit. ErrorDomain issue seemed to come out of nowhere for me in iMovie. Last Thursday, everything was fine. Sunday night, no more exports/file saves. I searched everywhere and went through all the offered solutions: trying a fresh project, creating a new library, restarting into Safe Mode then back, creating a temporary account, deleting iMovie and reinstalling and finally just giving in and upgrading from El Capitan to Mojave (which I'd avoided because of audio drivers). Hours and hours of wasted time, nothing fixed the error.


I'm so glad I found your post this evening. I knew immediately that it was the right solution, because I'd had to reinstall iTunes last Friday, the day after my last successful iMovie project. I can't believe I didn't make the connection.


After seeing your post, I found that MobileDevice.framework was indeed the only recently updated folder in PrivateFrameworks. Fortunately, TimeMachine had the original 2019 folder in my March backup. Took me awhile to figure out how to use Terminal in Recovery Mode to allow me to get past the PrivateFrameworks permissions (I never dig this deep into OSX), but you provided just enough information for me to find that csrutil would give me temporary access. Copied the older MobileDevice.framework folder over the new one, rebooted, went back into iMovie and was finally able to render my movie.


Again, thank you so much for digging into this. After two days of searching, I'm certain you are the only one who has identified this issue. It may not be the solution for all, but I bet it is the solution for anyone who has recently updated/reinstalled iTunes.

Similar questions

36 replies

Apr 24, 2020 10:58 AM in response to Vince Patton

Vince Patton --


I think that during this period of upgrades there are going to be glitches and conflicts as everything gets integrated, even with older but currently usable versions of Apple products. I suspect that many of these issues will be resolved over time. Meanwhile possibly some of those issues can be solved by using boot disks with older operating systems for running legacy software and earlier versions. Here's an interesting Apple bulletin that describes how to make a boot disk. Never tried it myself, but looks doable.


https://support.apple.com/en-gb/HT201372


-- Rich


Apr 26, 2020 4:18 AM in response to nicocaro

Hi! thank you so much for doing far better job than apple support! (they only advised to reboot in safe mode, or reset the OS)

But I have an additional problem: I don't have any Time machine back up!!! :-((

I reinstalled an old version of iTunes (12.6.2) but the problem is still there.

Do you have any idea how to solve that? it is very frustrating knowing the solution and not being able to making it happen.

Thanks a lot!


ps: I don't need to sync with iPhone

Apr 27, 2020 12:21 AM in response to donatien290

Hi Donatien, thanks a lot for sharing your solution.

Before doing something wrong I'd like to get your advise.

Do you think it will work if I modify mobile device.framework in safe mode just like you said with the command csrutil disable. Then restart normally. Then desinstall and reinstall iMovie.

I don't have any Time machine back up, so I don't have any old version of mobile device.framework.

What do you think?

many thanks

May 8, 2020 9:30 PM in response to namaquaman

You guys are simply gods to me today. You not only figured out the absolute only solution to this issue for me, but also solved another error screen that popped up for LOGIC 9 pro. I went back in memory on kg time machine & realized what the culprit was. After repairing the problem as for your solution, I realized it’s due to an iTunes update. Because after a few bites the machine told

me there was an update for iTunes. I dare not install that now. I think by replacing the file back to your suggestion I must somehow return something g I iTunes backwards. It all working now so I won’t update iTunes now. I can not thank you enough 🙏🙏🙏

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.

iMovie 10.1.6 on El Capitan - sharing/rendering returns CompressorKit. ErrorDomain error -1 - Caused by MobileDevice.Framework provided only in X86_64 and not anymore in i386 architecture.

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