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

exp publish throws 'socket hang up' exception on gitlab CI #909

vardium opened this issue Nov 3, 2017 · 3 comments


None yet
2 participants
Copy link

commented Nov 3, 2017

I am trying to prepare a 'Continuous Integration' environment for my expo project. On gitlab CI, I am getting following exception on exp publish.

$ exp login -u ${EXPO_USERNAME} -p ${EXPO_PASSWORD}

Success. You are now logged in as ****.

$ exp publish
[exp] Unable to find an existing exp instance for this directory, starting a new one...
[exp] Starting React Native packager...
[exp] Scanning folders for symlinks in /builds/****/****/node_modules (13ms)
[exp] Loading dependency graph.
[exp] Running packager on port 19001.
[exp] Publishing...
[exp] Building iOS bundle
[exp] socket hang up
[exp] Set EXPO_DEBUG=true in your env to view the stack trace.
ERROR: Job failed: exit code 1

Here is my .gitlab-ci.yml configuration :

image: node:6.11.0

  - build
  - deploy

  - npm i -g exp --silent

  key: ${CI_PROJECT_ID}
  - node_modules/

  stage: build
    - npm i --silent

  stage: deploy
    - master
    - /^release\/.*$/
    - exp login -u ${EXPO_USERNAME} -p ${EXPO_PASSWORD}
    #- exp build:android
    - exp publish


This comment has been minimized.

Copy link

commented Nov 3, 2017

Find the solution on forum.

Adding the following option to app.json solved the problem.

"packagerOpts": {
      "nonPersistent": true,

@vardium vardium closed this Nov 3, 2017


This comment has been minimized.

Copy link

commented Nov 18, 2017

However, this option disables hot & live reloading, spent hours to solve why it is not reloading.


This comment has been minimized.

Copy link

commented Feb 17, 2018

Just don't use non ASCII characters in path to your project.
It helped for me.

@lock lock bot added the outdated label Jun 15, 2019

@lock lock bot locked and limited conversation to collaborators Jun 15, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.