Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when upgrading to XCode 11.4 #13

Open
evanb2 opened this issue May 20, 2020 · 2 comments
Open

Errors when upgrading to XCode 11.4 #13

evanb2 opened this issue May 20, 2020 · 2 comments

Comments

@evanb2
Copy link

evanb2 commented May 20, 2020

Apple is requiring all apps to be built using iOS SDK 13+ starting June 30th, which requires XCode 11.X. The default XCode image for this Orb is currently 10.1. Manually setting the ios executor is throwing an error when building in CI.

My project's config.yml:

custom_executor:
    name: react-native/ios
    xcode_version: '11.4.1'

Error in CI:
2020-05-20 at 11 35 AM

Detailed error in the logs:

error `fsevents` unavailable (this watcher can only be used on Darwin). Run CLI with --verbose flag for more details

This seems to be caused by using yarn instead of npm in CI.

The yarn install step shows the following error:

Error running install script for optional dependency: "/Users/distiller/react-native/node_modules/fsevents: Command failed.

Using npm install succeeded with no errors.

  1. Is there another fix for this besides using npm?
  2. If not, what's the easiest way to override that using this Orb?
  3. Is this Orb still maintained?
@evanb2
Copy link
Author

evanb2 commented May 22, 2020

Looks like specifying node v10.11.0 also fixes the issue. Although the only way I was able to get that to work with the react-native/ios job was by doing:

pre_build:
    - run:
        name: Force specific nodejs version
        command: |
            export NODE_VERSION=$(cat .nvmrc)
            curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.35.1/install.sh | bash -s -- --no-use
            echo 'export NVM_DIR=$HOME/.nvm' >> $BASH_ENV
            echo 'source $NVM_DIR/nvm.sh' >> $BASH_ENV
            echo 'nvm install v10.11.0' >> $BASH_ENV
            echo 'nvm alias default v10.11.0' >> $BASH_ENV
            rm -rf node_modules
            yarn install

I tried overriding the react-native/node executor but it didn't work:

- react-native/node:
    name: node
    custom_executor:
        name: react-native/node
        version: '10.11.0'

@cball
Copy link
Member

cball commented May 24, 2020

Hey @evanb2! Appreciate the detail, and sorry you're having trouble with it. We're using the following executors in a recent project and things seem to be working ok:

executors:
  node:
    docker:
      - image: circleci/node:10.16.0-stretch
        environment:
          TERM: xterm
  android:
    docker:
      - image: circleci/android:api-28-node
    environment:
      - _JAVA_OPTIONS: '-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap'
      - GRADLE_OPTS: '-Dorg.gradle.daemon=false -Dorg.gradle.jvmargs="-XX:+UnlockExperimentalVMOptions -XX:+HeapDumpOnOutOfMemoryError"'
      - BUILD_THREADS: 2
      - FL_OUTPUT_DIR: output
  ios:
    macos:
      xcode: 11.3.1
    shell: /bin/bash --login -o pipefail
    resource_class: 'medium'

We'll take a look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants