Cinema 4D (R19) won't launch on my Mac
So, this has just happened... all of a sudden and in the middle of a project. I closed up everything, shutdown my MBPro and left for a couple of hours for lunch. I came back in the evening and now when I click the C4D it just give one bounce with the little grey circle below it and no more. I can't launch it nor can I actually launch its installer in order to fix or reinstall the software.
I have never before had such issues with C4D or any other software for that matter. Obviously I've changed nothing in my system, especially not since this morning: no updates, installed nothing else, etc.
I've since tried everything: deleting the contents of my Cache, Launch Agents, Saved Application State, Launch Daemons, etc., folders; I've reset the System Management Controller; I've reset the NVRAM; I've launched in Recovery Mode and ran First Aid on my drives... I even followed the only online recommendation I found that somewhat describes a similar issue and I deleted the Mesa folder located in resources/libs/osx... All to no avail.
I'm mid-project and now I have a launching issue that I don't seem to find that anyone else online has had and I don't know what to do. Any input will be extremely appreciated!
P.S. As I said, I'm running R19. I Specifically had R19.024 installed last time I checked, but I do remember installing updates a while back; however, as you can imagine I can't even see what my specific version is, as it doesn't allow me to load anything. And the MacOS I'm running is Sierra 10.12.6.
ah interesting, me too. Mac at work that I have everything from R20 back to R10.5 installed on. Yesterday suddenly R20 wouldn't launch. I had a bit of time today and R16- R20 won't launch and R10.5 - R15 will launch. I'm not working on anything so I haven't done any investigation other than that.
At home (PC, switched) R21 sometimes won't start but will after a reboot but R19, R20 start no problem.
On the Mac (old Mac Pro early 2008 so OSX 10.11.6 is the latest possible) since it's 5 separate versions that won't start it can't be a reinstall... the only thing I can think of is I did the update to iOS 13 on the phone the night before and when I plugged it in to the Mac yesterday it needed to do an update so the iPhone would be able to connect....
Did you have to do a small install to get the new iPhone OS to connect?
As a matter of fact, yesterday I had to update my iPhone by connecting it to my Mac. I hadn't thought of that because C4D was working fine today; but the truth is last night I didn't shutdown my Mac, only put it in Sleep mode... So I think C4D the first time I exited C4D was today. Which could explain why (if the issue actually is, as you say, from the iPhone update) it not launching occurred only just now.
BTW, this is what I'm finding in the Console as I try to launch:
Don't know if that can help find the issue.
I too tried to launch C4D on my PC (which is only my rendering machine) and there was no issue there. So it's only limited to my Mac and the fact that you mention you too had to update your phone (added to the fact that I NEVER update my phone using my MBPro, and I believe this is the first time I've done that) makes me think that's the common variable...
I would send that into Maxon support, it doesn't mean anything to me but it may well mean something to them.
I think the issue lies here:
After several hours' research... 😖... I think I've pinpointed the issue: apparently it has to do with the fact I was prompted to update iTunes when I was trying to update my iPhone and that resulted in a corruption of the MobileDevice Unix Executable file in System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/. At least that's the most plausible explanation I found online. However, I can't actually solve it, as the steps everyone says one should follow include deleting these files and my Mac won't allow me to do so, as it says they're needed for the OS to work properly... So that gets me nowhere. I've tried reinstalling iTunes, even downgrading (it didn't let me) but nothing has changed: C4D still won't open at all.
This has happened to me a few times in the past for a variety of reasons.
Usually it's a corrupt Cinema 4D.prf file or the executable bit on the C4D executable file was flipped during a restore from the backup server.
You can run this in terminal to make sure the executable bit is set:
If that doesn't work and you want to tamper with the problematic OS core files, you can mount the system as read/write for the current session temporarily and then change the file name with these terminal commands:
Hi. Thanks for your input.
That first option seems to have actually made things worse... It now directly says "The application 'Cinema 4D' can't be opened', and the Cinema 4D.app/Contents/MacOS/Cinema 4D executable file is now no longer an executable, and when it opens (now in TextEdit) it displays gobbledygook instead of opening up in Terminal and displaying the processes... I'm really out of my depth here, so I don't know if I can revert this or if there's another step I'm missing...
On the other hand, the second option has the same result as trying to change the permissions through Get info, it tells me "Operation not permitted"... For some reason my Mac just doesn't want to allow me to either delete that framework or give myself permission to do so. My account does have Administrator privileges, so I don't know what's going on.
I've also tried finally installing R20 (I was putting it off because I had no time to install it and migrate everything... but now I'm stalled anyway) and the result is the same as trying to re-install R19: I click the installer, it bounces an icon once on the dock, and then it fizzes out, doing nothing. So I must assume it too tries to use that corrupt framework. (Plus, this just proves to me that it has nothing to do with the C4D executable, as the same thing happens with both the R19 and R20 installation executables, too.)
Ok. I got it back to being a Unix Executable File after some research online on how to manage that:
(It seems pretty obvious now 😏)
So now the only thing I have to find out is how to deal with the MobileDevice.framework if my Mac won't allow me to change it, move it or delete it! But it seems to work right outta the box for everyone else, so I can't find any info on that...
Sorry about that. I now see I typed the wrong flag on the change mode command. Glad you were able to fix it.
Here are some more things to test that I always recommend when troubleshooting:
1. Double-click that executable directly "/Applications/MAXON/Cinema 4D R19/Cinema 4D.app/Contents/MacOS/Cinema 4D"
This will launch a terminal window and spit out all the debug info you need.
Look for any signs at the end when it halts other than the message about the MobileDevice package.
2. Create a new user profile on the Mac and login and go through the initial setup stuff.
Immediately try to start up C4D. If it works as expected then you know something in your main user profile is the cause.
If it still doesn't work, then it is either the application install or the OS.
In that case, rule out the application first by deleting every trace of it in:
3. Try to delete the problem file again (for testing purposes as temp solution)
You will probably have to disable system integrity protection if not already.
First, I'm assuming you've performed first aid on the disk from within system recovery?
Do that by shutting down, then powering up and holding down command-R for a while.
In system recovery open up disk utility and run first aid and see if it is able to detect a problem.
If it comes back clean then you can try to move or rename the file after disabling system integrity protection and then following the steps from earlier.
While still in system recovery, launch the terminal and type in the command:
After pressing return you should get a confirmation that it will take effect after reboot.
Do that and boot up normally.
If you are able to move or rename the file, then in terminal you can reenable SIP with:
After you reboot, system integrity protection will force the system files back to their original state which should hopefully fix it (if that is truly the problem).
I just got this response from Maxon Support
this looks like a problem with the operating system. We have been informed that this can be the result of an macOS security update that occurs after adding an iphone to link to the machine.
The known work around for this is currently to upgrade your operating system to 10.14. I am not aware of any others, but a reinstallation of the current operating system may also fix the problem.
Hi, guys! I'm so thrilled to be able to come back and say that finally I managed to resolve the issue! And even more thrilled that I wasn't forced to upgrade OS, as I haven't had time to thoroughly research the consequences of Mojave or Catalina...
Anyway, I thank you all very much for your input! It's been a very tense couple of days but all's well that ends well, I guess. This is what finally worked for me:
I had already tried some of the things you recommended and then tried the ones I hadn't but to no avail. In the end, the fix was getting rid of the offending framework, but with a twist. I'll explain in detail:
Last night, when I opened the executable directly I got the Terminal window with the list of precesses, and everything was fine except for the error I mentioned in a previous post, which pointed toward the MobileDevie.framework. There were no signs at the end; the process simply stopped and exited, but there was no other mention of anything weird. So I had to assume this was the issue.
As I pointed out, after extensive research my conclusion was that there had been a change that had occurred when I tried to upgrade the iOS on my iPhone, which had forced me to also upgrade iTunes and, as Maxon have pointed out to @Brian Jones, do a security update. Based on all this and thanks to @Brian Jones' post on what Maxon had told him I was 99% sure the only way to fix the issue was to get rid of that framework or substitute it with that of my other MBPro which had had no such upgrade or update.
However, the issue was that my Mac simply wouldn't allow me to rename, swap or delete the framework. Thanks to @Sam Treadway's guide in point 3 on how to get my Mac to grant me control in order to get rid of these files, I was able to do just that. However, I found that just renaming (or getting rid of) the actual MobileDevice executable wasn't enough, as rebooting didn't create a new one and then the error just changed to not being able to find the executable instead of not being able to find a symbol within it. So I got rid of the entire MobileDevice.framework (i.e. the file that's in the PrivateFrameworks folder) and I brought in the MobileDevice.framework from my other computer that had had no upgrade or update, as I said.
And that did the trick!
So, to recap, step by step: How to get C4D to work again if you have updated iTunes etc.?
1) Go into /Applications/MAXON/Cinema 4D R19/Cinema 4D.app/Contents/MacOS/ and open the Cinema 4D executable. This will open it up in a Terminal window and make sure the problem is in fact something to do with the MobileDevice.framework.
2) Get the entire MobileDevice.framework from another Mac (that's running the same OS, and hasn't been updated or that can run C4D without a problem) or from your TimeMachine backup made before updating. You can find it in /System/Library/PrivateFrameworks/
3) Shutdown your Mac and turn it back on while pressing the CMD+R keys on your integrated keyboard. When the Apple logo appears you can release the keys. This will open Recovery Mode.
4) Recovery Mode will prompt you to choose your preferred language: do so. Then go to the top bar, go to Utilities > Terminal.
5) In the Terminal window type: "csrutil disable" (without the quotation marks) and press Return.
6) A confirmation will appear: "Successfully disabled System Integrity Protection. Please restart the machine for the changes to take effect." Do so: restart your computer and let the OS load normally.
7) Now you can into you /System/Library/PrivateFrameworks/ and move out or erase the MobileDevice.framework and in its place paste the MobileDevice.framework you retrieved from the working computer or OS backup
8) Restart your computer and go back into Recovery Mode, open up the Terminal and type: "csrutil enable" (without the quotation marks) and press Return. This will re-enable System Integrity Protection.
9) Restart and let the OS load as usual and 🤞 you should now be able to launch C4D once again!
10) If everything goes according, permanently erase the old framework you deleted or moved out of its place and don't update iTunes or run security updates until you are ready to upgrade your entire OS—or at least without having a working copy of MobileDevice.framework at hand and being prepared to repeat these steps to save your life!
Having said all this, I must admit I'm somewhat disappointed at Maxon that they've made their software dependant on a Private framework, which is supposed to be "private" and for Apple's use, which means that any change to it will possibly make their software unusable, as it surely did in this case. I still don't understand why C4D needs to have anything to do with the Mobile Device framework... but perhaps all I'm doing is showing how little I know about the matter.
Anyway, once again thanks a million for your help, guys! And I hope this post might help out someone else and spare him/her several headaches!
I just may have found an alternate end process to solve this problem: reinstall a previous version of iTunes.
Just as noted in Xavier's message above, you most likely will need to disable SIP via Recovery Mode. This is important because you'll need to manually delete the MobileDevice.framework file in order to replace it with an older version. Simply reinstalling iTunes (12.8.2) without first deleting the framework will not suffice, since installer packages will not overwrite certain files if a newer version is already present.
Manually restoring the MobileDevice.framework file from a backup may not be sufficient if the backup is not recent. It's my guess, but there may or may not be compatibility issues with the framework file (if it's too old) and the iTunes version is newer. In my specific case, my last backup is from almost two years ago, so manually replacing the framework file was not an option for me, despite STILL being on Sierra (10.2.6) for eGPU reasons.
Lastly, to note, the older framework file that works is listed as version 988.222.1 (created Jan. 10, 2019), and the offending version that breaks Cinema 4D is version 1190.9.1 (created Aug. 29, 2019). You can check the version numbers via Get Info in the Finder.
Nonetheless, backup your machine regularly for your safety and sanity! Thank you all for your solutions and bringing this to light.
You can download older versions of iTunes from Apple's Support page: https://support.apple.com/downloads/itunes
Hi Xavier, I ended up on your post while troubleshooting Logic Pro not loading customized plugins, with the same root error pointing to MobileDevice.framework. Completely different application, but your troubleshooting step-by-step helped me solve the problem. Many many thanks!
Hi, Jake! I'm very glad you were able to solve your issue as well!
And thank you very much for letting me know you found the troubleshoot useful, you're very kind! I often benefit from the knowledge of others here at Creative Cow but there are so many knowledgeable people around, and then the stuff I do is usually so specific and niche, that it's not often I get to chime in and return the favor! So I'm very glad something good came of it!
...So this is how I managed to bungle it up today.
So I found this thread after I deleted my C4D applications but now none of my installers will open. Do we think this fix will allow me to run R18-20 installers?
Same. Went to boot up R16 this morning (after reluctantly allowing that Apple iPhone update) and then c4d suddenly won't open. Get one slight bounce in the dock then it disappears. Tried the reinstallation iso file and it's strangely not working also.
Doing a Restore from Time Machine backup right now. Any help to getting this fixed (and being able to get back to work) would be appreciated! So frustrating..
Hello, @Tim Reynolds. In my last post above you'll find step-by-step detailed instructions to solving this issue. And considering the security update is culprit in your case as well, in theory you should be able to solve it just as I did, and have no further trouble. I didn't restore from Time Machine but I guess it should restore the MobileDevice.framework to one that plays well with C4D.
If you guys have problems getting a "good" copy of the framework perhaps I can upload here the one I used which worked for me. I'll need to check and see if that's allowed.
...So this is how I managed to bungle it up today.
Good morning guys ... I read with regret that you also had this problem ... I unfortunately do not have time machine activated so I can not recover the file to replace ... and as maxon says I can not reinstall 10.14 because having a mac pro early 2009 is not compatible ... it is a big problem this!
Then yesterday panicked I deleted the entire folder itunes and I hope that this does not create more problems!!!
If you have other solutions I would be happy to read them...
Hi, Eros! Do you have access to any other Mac running the same or a similar OS? Perhaps a friend's?If you do, you can get the file you need to substitute. You don't need to get rid of the entire iTunes folder.
If you haven't already, check out the step-by-step instructions to solve this issue I posted in my previous-to-last post above.
Hope you can solve this soon, too!
...So this is how I managed to bungle it up today.
Thank you so much for your explanation! I have only one problem, I have no back up or another osx system where I can get the MobileDevice.framework file. You where saying that you perhaps can give your file. Do you think that is possible?
Sorry for the delay! I've been traveling shooting material for the last week or so, so I haven't kept up to date online. You've probably solved this by now but, for what it's worth, to you or anyone else, here goes the working framework file:
Hope this helps!
P.S. I've had to compress it because, otherwise, the CC uploader wouldn't let me select the file. I hope that doesn't mean these kinds of files aren't allowed on CC, only project files.
...So this is how I managed to bungle it up today.
Had the same issue when I ran that little updater for iTunes for ios13.
Was the definite cause and effect - not sure who is at fault, I had the error in the console having to do with the "code signature" - so, did Apple somehow depreciate C4D, or was C4D code signature bad and just waiting to break?
I luckily keep a clone of my drive and replaced 3 frameworks in the System/Library/PrivateFrameworks. I replace the following with version from May 25th (I'm on El capitan BTW)
These were the ones 'updated' by the lousy little installer from Apple.
All works again - but will it be broken again?