DYLD, [0x1] Library missing

[jlarvers]

Hello,

I just bought CodeKit installed on MacOs 10.13.6 (17G14042).

Normally, Codekit works with 10.13+

When I want to start it, don’t work and I have the following error:

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/lib/swift/libswiftCore.dylib
  Referenced from: /Applications/CodeKit.app/Contents/Frameworks/libswift_Concurrency.dylib
  Reason: image not found

Can you help me ?

Bests.

[jlarvers]

Codekit's response, by email (not on this ticket):

Hi Jean-Luc,

There is an issue with Apple's Swift framework that is causing this on older versions of macOS. Your best bet is to update to macOS 10.15+. (Your current version has been obsolete for almost half a decade.)

-Brian

I do not intend to change OS to run Codekit which, according to your requirements, should work on my current OS 10.13.4

On the home page of your website, you write:

"Free Trial, NO subscription. Requires macOS 10.13+".

And on the page, Buy a License, you write:

"I realize that CodeKit requires macOS 10.13+ and does not run on Windows. I have read and accept the License Agreement."

Can you correct this false information on your website by specifying that Codekit only works from 10.15+?

Thank's.

[bdkjones]

Sigh. Again, this is a bug in the version of Xcode that was used to build CodeKit 3.15.1. That version of Xcode failed to include the correct Swift runtime, which affects only those people still using ancient versions of macOS.

The BEST solution is to update your Mac to a modern version of macOS. Running an OS that's four years out of date is, unsurprisingly, going to leave you open to headaches.

The alternate solution is to download CodeKit 3.15, which is available from https://codekitapp.com/updates/ and was built with a different, non-buggy version of Xcode.

Either way, I anticipate that Apple will fix Xcode and the next release of CodeKit will again correctly link Swift frameworks for those folks still on ancient versions of the OS. So, CodeKit does support macOS 10.13+, it's just that you happened to grab a version that's been built with buggy tooling from Apple. When Apple Engineering fixes their problem, I can fix this one.

[bdkjones]

Additionally, while I do my best to keep old versions of macOS in play (CodeKit JUST dropped support for 10.11 and 10.12 a few months ago) my official support has always been the current version of macOS and one version back. That's a two-year window. It's all I can manage—I don't have a giant QA department with 17 people and 43 Macs all running various configurations of the OS. I have me and two Macs. I do not officially test releases on macOS versions older than two years because I simply can't. I receive reports from the few people who are still on those old versions and then fix the problems they encounter as best I can.

[bdkjones]

Finally, you aren't even running the latest version of macOS 10.13!

You should REALLY visit this page: https://support.apple.com/en-us/HT201222

Those are the HUNDREDS of security vulnerabilities to which you are leaving yourself open by keeping your Mac out of date. Many of them are zero-interaction vulnerabilities, meaning that all you have to do to get your machine compromised is visit the wrong website. Apple itself has ended support for macOS 10.13; they no longer issue security updates to cover vulnerabilities. That makes it dangerous to remain on 10.13.

[jlarvers]

I got Codekit 3.15 by following the link you just sent me. It works fine on my OS 10.13.4. Thank you for your great responsiveness.

[bdkjones]

Glad that stop-gap worked, but you should REALLY visit that link I posted above and see some of the vulnerabilities that are 100% unfixed in 10.13.4. You're playing with fire, my friend.

[jlarvers]

For a lot of reasons, I keep an OS 10.13.4 with software that can't work elsewhere.

It is true that it is disabling now.

Anyway, thank you for the feedback and solution 2 :-)

-- Jean-Luc ARVERS AJLSM 05 57 14 25 20 @.**@.>

Le 3 déc. 2021 à 08:34, Bryan Jones @.**@.>> a écrit :

Glad that stop-gap worked, but you should REALLY visit that link I posted above and see some of the vulnerabilities that are 100% unfixed in 10.13.4. You're playing with fire, my friend.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/bdkjones/CodeKit/issues/676#issuecomment-985281326, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJAUKAVGGTKKOZNHKQJSITDUPBXJBANCNFSM5JHI3XOA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.