# The default \`osx\_image: xcode9.4\` is now unusable because MacOS 10.13 is EOL
**URL:** https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628
**Category:** macOS
**Tags:** bug, homebrew
**Created:** [November 19, 2020, 3:13pm UTC](https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628 "2020-11-19T15:13:10Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jeroen](https://travis-ci.community/u/jeroen)
#### Post date: [November 19, 2020, 3:13pm UTC](https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628/1 "2020-11-19T15:13:11Z")
As of the release of MacOS 11.0 earlier this week, Apple and Homebrew no longer support MacOS 10.13. This means homebrew no longer provides binaries for MacOS 10.13, and on those systems, everything has to be built from source.
However `osx_image: xcode9.4` is still the default `os: osx` image. As a result, many jobs fail because they have to start building all the brew packages from source.
---
### Author:  [@larsbrinkhoff](https://travis-ci.community/u/larsbrinkhoff)
#### Post date: [December 3, 2020, 7:20am UTC](https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628/2 "2020-12-03T07:20:56Z")
I have run into this as well. Is this being fixed?
---
### Author:  [@tresf](https://travis-ci.community/u/tresf)
#### Post date: [February 5, 2021, 9:25pm UTC](https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628/3 "2021-02-05T21:25:55Z")
It’s now February 2021 and the default XCode image is too old to work with Homebrew without running into timeout failures. Travis, this is a lot of CPU cycles spent that can be avoided by bumping the default image.