Debug release stopped taking changes

alfredopacino · May 22, 2018, 12:44am

The error is “…socket hang up…”
Well, it’s pretty common error

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

opened 01:15PM - 03 Nov 17 UTC

closed 02:48PM - 03 Nov 17 UTC

I am trying to prepare a 'Continuous Integration' environment for my expo projec…t. 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] [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 stages: - build - deploy before_script: - npm i -g exp --silent cache: key: ${CI_PROJECT_ID} paths: - node_modules/ build: stage: build script: - npm i --silent deploy: stage: deploy only: - master - /^release\/.*$/ script: - exp login -u ${EXPO_USERNAME} -p ${EXPO_PASSWORD} #- exp build:android - exp publish ```

github.com/expo/expo

nonPersistent in app.json disables hot reload

opened 10:17PM - 19 Oct 17 UTC

closed 07:47PM - 09 Oct 19 UTC

BenBrostoff

docs project: react-native

First off, thanks for a great project Expo team. I noticed from a clean `crea…te-react-native-app` that hot reloading will break with the following `app.json` configuration: ``` { "expo": { "sdkVersion": "21.0.0", "packagerOpts": { "nonPersistent": false } } } ``` This makes sense, as in the `react-native` source it looks like a `watch` option is being disabled if args exist for [`nonPersistent`](https://github.com/facebook/react-native/blob/34487c059192129db07608af4eb27cfad22b2d06/local-cli/server/runServer.js#L205). I think a number of Expo users are leveraging `nonPersistent` for [CI purposes](https://forums.expo.io/t/what-do-you-use-for-testing-and-ci-for-expo-rn/850/3), and presumably also want hot reloading when developing locally. I think it makes sense to document `nonPersistent` as it can have some important consequences. Would love to help here on the documentation front if this sounds like a good idea!

Topic		Replies	Views
getting latest changes on Android device?? (Deprecated) Help: ExpoKit	3	812	February 26, 2019
File changes not persisting Expo Development Tools	2	486	July 26, 2019
Android debug build stopped running Expo SDK	10	312	May 20, 2023
Android release with Splash problem (Upgrade to Expokit 33) (Deprecated) Help: ExpoKit	9	712	August 3, 2019
After ejecting from expo taking too much time to build on android studio Expo Development Tools	3	1428	July 6, 2018

Debug release stopped taking changes

Related Topics