Crashes on macOSX 10.11 El Capitan? [1.14.0] [June 2021] [SOLVED]

I have an older Macbook Pro (15 in, late 2011) which used to run Zwift.

I got hit earlier this year by the bug which required disabling WiFi, starting the app, then re-enabling it.

However now it seems the latest version no longer launches at all. Attempted some of the fixes in the forums including a full reinstall, however the app immediately crashes when I click “Let’s Go” and spits out the following

[16:55:57 2021-06-15] Launcher: Update Complete.
[16:55:57 2021-06-15] Launcher: Webview loaded some URL.
[16:55:58 2021-06-15] Launcher: Webview loaded some URL.
[16:59:10 2021-06-15] Launcher: Webview loaded some URL.
[16:59:10 2021-06-15] Launcher: Found Zwift Scheme.
[16:59:10 2021-06-15] Launcher: Access Code Received.
dyld: lazy symbol binding failed: Symbol not found: _objc_alloc_init
Referenced from: /Users/me/Library/Application Support/Zwift/ZwiftMacCrashHandler
Expected in: /usr/lib/libobjc.A.dylib

dyld: Symbol not found: _objc_alloc_init
Referenced from: /Users/me/Library/Application Support/Zwift/ZwiftMacCrashHandler
Expected in: /usr/lib/libobjc.A.dylib

[1184:32844:20210615,165911.566066:ERROR file_io.cc:91] ReadExactly: expected 4, observed 0
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
Referenced from: /Users/me/Library/Application Support/Zwift/ZwiftApp
Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
Referenced from: /Users/me/Library/Application Support/Zwift/ZwiftApp
Expected in: /usr/lib/libSystem.B.dylib

2 Likes

Having similar issues with the latest update as well. My Zwift app updated on my MacBook (Early 2015, El Capitan), and when I click on the ‘Let’s Go’ button, nothing happens - no error message but the app also doesn’t launch. This is similar to the issue I experienced with the last update back on May 19th. I’ve tried uninstalling and reinstalling Zwift, restarting my laptop, clearing the cache on Safari, and nothing is working.

1 Like

Looks like they ended support for Yosemite. That may have something to do with it.

1 Like

I completed a ticket with tech support and it seems like an 8GB memory requirement was added as well. My MacBook is 4GB so I’m SOL it seems. I was a week away from finishing up a training plan, this is just bad timing :frowning:

1 Like

I previously tested the game running fine (albeit with low quality textures) on as little as 2GB on a PC, so this sounds like codswallop to me. I’ll have to test it again.

I had plans to upgrade my laptop but a little notice would have been nice. I was hoping to see if there were any back-to-school specials later in the summer. I wish we could use the previous build - I just opened Zwift on my phone and it gave me the option to update now or within 5 days. This just sucks.

Yup, totally agree. Zwift should give notice about this. There is no reason to not disclose this early, give people a months watching @shooj ?

1 Like

Hi @Neil_UK

It was posted beginning of the month.
Ending support for macOS v10.10 [June 2021]?

1 Like

El Capitan is new enough though. :wink:

Not working on El Capitan - Zwift states that is the minimum requirement…so should still work - very frustrating…

1 Like

Thanks for the previous post Neil! I’d also like to know the answer for the lack of notice. Even games on my phone give out warnings months ahead of time of when support for certain devices or operating systems will end.

The training plan is one thing, I have a 2 hour+ race this weekend which is the last in the series - it’s going to be painful on a smaller screen :grimacing:

Running El Capitan 10.11.6 so I should have minimum requirement as well but I am also unable to launch the app. Not getting any error message just crashes.

Fair enough then

As the last update, issues on MacOS as well. As soon as I click “Let’s Go” Zwift crashes.

6 Likes

Hello @Oliver_King2 @Vicky_L @Steven_Scott1 @D_Winn @_Gil_SantaMaria and everyone on this thread.

Thanks for bubbling this issue up. We’re treating this bug with the highest priority.

We’re having difficulty reproducing this crash. This may indicate that it’s not affecting every OSX El Capitan (10.11) user across the board. Is anyone using El Capitan without problems? Please chime in if so.

Secondly - because the crash happens during the application launch phase - our servers are not capturing the crash data from your computers. If you are tech savvy (@Oliver_King2 I’m looking at you sir) and would like to send us your crash event logs, we’d love to investigate your specific computer.

Please follow the instructions on this Support Hub article, and attach your crash logs in an email to logs@zwift.com. If you would put “El Capitan Crash” in the subject line, that’d be helpful. Thanks!

1 Like

I have El Capitan 10.11.6 and Zwift won’t work after updating today. Thoughts?

5 Likes

That is what I have. Tech support said Zwift won’t work on my computer with this new update. They said, find another device to run Zwift on.

1 Like

Same issue here. Did you find a fix?

The newest update doesn’t work on my MacBook with El Capitan either. I put in a ticket with support and was told the newest version of the app requires 8GB of RAM. That’s kind of an expensive fix … I don’t remember getting any warnings about that :frowning: