Häufig gestellte Fragen

Cinema 4D all of a sudden won't launch on my Mac? (iOS 13 related)

Have you recently updated your iPhone to iOS13 and hooked it up to your Mac?

If so this update prevents Cinema 4D launching, including the binary.

The issue appears on older version of macOS when an iOS13 device is connected to them via iTunes. Only the more recent macOS versions are compatible for that.
As most software we rely on frameworks of the operating systems. In this case the incompatibility between old macOS versions and the newest iOS leads to broken internal dependencies, which then again can surface in other software - as in this case Cinema 4D.

Details as far we know them
  • The offending file is a macOS private framework called MobileDevice.framework. Cinema 4D seems to indirectly use it via another macOS framework which relies on it.
  • the defective dylib (and frameworks) get installed, if a customer tries to backup an iOS 13 device on his computer in iTunes - with an older macOS without iOS 13 support version.
  • You usually can't copy dylibs new macOS versions to an older OS though (due to changes in the OS, potentially the System Integrity Protection and - in this case - the fact that libsystem.b.dylib is there in multiple versions with potentially other unknown private dependencies).
Known solutions
  • Repairing: Installing an older iTunes version seems to overwrite the defective OS components (e.g. iTunes 12.8.2)
  • Reparing / Avoiding: Installing a new macOS version (10.14 / 10.15) seems to replace the defective OS components by ones, that don't have this dependency to the mobile framework (and therefore don't prevent the startup of Cinema)
  • Avoiding: Using iCloud backup instead of a backup on the computer avoids this issue

There have been hints around to manually replace framework files, but you usually can't copy dylibs of new macOS versions to an older OS though (due to changes in the OS, potentially the System Integrity Protection and - in this case - the fact that libsystem.b.dylib is there in multiple versions with potentially other unknown private dependencies).

image

Bitte warten!

Bitte warten... es dauert eine Sekunde!