electron: v2.0.3 Electron doesn't run: dyld: Symbol not found: _CIDetectorTypeText

Electron Version: 2.0.3
Operating System (Platform and Version): macOS 10.10.5 (Yosemite)
Last known working Electron version: 2.0.0

Expected Behavior Electron App should start after running the command: npm run start

Actual behavior App doesn’t start and the following message appears on console:

dyld: Symbol not found: _CIDetectorTypeText
  Referenced from: /Users/renato/Projects/smart-press/node_modules/electron/dist/Electron.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
  Expected in: /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
 in /Users/renato/Projects/smart-press/node_modules/electron/dist/Electron.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework

To Reproduce https://github.com/renatop7/electron-quick-start

$ git clone https://github.com/renatop7/electron-quick-start
$ npm install
$ npm start

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 18 (5 by maintainers)

Commits related to this issue

Update deps, including electron@2.0.4, fixes crash on macos yosemite electron/electron#13404 — committed to irccloud/irccloud-desktop by jwheare 6 years ago

Most upvoted comments

@benlancaster I believe it was the MacOS SDK version. See https://github.com/electron/electron/blob/003a92e0990fa4ba1bd7b93450eb3afae0533090/docs/development/build-instructions-osx.md#macos-sdk for the right sdk to use

jkleinsc on Sep 20, 2018

It turns out we used a different VM to build 2.0.3 vs the VM used to build 2.0.2 and earlier releases. 2.0.4 was released today using the same VM as 2.0.2, so this issue is resolved in 2.0.4

jkleinsc on Jul 3, 2018

I think I can track down a VM in order to replicate the issue and verify any fixes.

I set up a Yosemite VM, and I verified that I can reproduce the issue when using the test app with Electron 2.0.3 and that I cannot reproduce it with Electron 2.0.2. This confirms @renatop7’s findings in https://github.com/electron/electron/issues/13404#issuecomment-399974110. (Thanks, @renatop7!)

@alexeykuzmin kindly pointed me to the specific XCode version and macOS SDK version necessary to mimic an official Electron build. I’m working on getting those things set up, and then I can hopefully bisect the changeset (311f7ac…4aedc2c) to identify the specific commit that introduced the issue. 🤞

jasonrudolph on Jun 28, 2018

Without a machine to replicate this on though it’s gonna be pretty hard to track it down. A git bisect is what we really need to do here

@MarshallOfSound: I think I can track down a VM in order to replicate the issue and verify any fixes. I’m willing to do the git bisect to track down the root cause, but I’ll have to ask for some guidance regarding the specific steps. 🙏 I think I’d need to bisect the changeset (https://github.com/electron/electron/compare/311f7ac6bb0f25e6beb1279564ea452fa538f4a5...4aedc2c21a17a178d5bbf4d8391b8216f56cfc15), build Electron at each SHA that git bisect stops on, and then use the resulting build as the Electron version in @renatop7’s test app. Does that sound right?

If so, once I build Electron at a given SHA, how can I tell the test app to use that locally-built version of Electron?

jasonrudolph on Jun 26, 2018

Looks like earlier Atom 1.28 Beta releases with 2.0.0 and 2.0.1 were working, more evidence that it’s a 2.0.3 issue: https://github.com/atom/atom/issues/17565#issuecomment-400064788

daviwil on Jun 25, 2018