After upgrading, I’ve noticed that everytime I expo publish, I also have to restart my local “expo start”.
Before I don’t remember them being linked…but it’s a very nagging inefficiency in my developer workflow.
Is anyone else experiencing this?
After upgrading, I’ve noticed that everytime I expo publish, I also have to restart my local “expo start”.
Before I don’t remember them being linked…but it’s a very nagging inefficiency in my developer workflow.
Is anyone else experiencing this?
osx 10.14.6
Has been happening to me as well the past few weeks
Expo CLI 3.27.12 environment info:
System:
OS: macOS 10.15.6
Shell: Unknown - /usr/local/bin/fish
Binaries:
Node: 14.6.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.6 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.8.4 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 26, 27, 28
Build Tools: 28.0.3
System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5199772
Xcode: 12.0.1/12A7300 - /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config: ^0.12.22 => 0.12.31
expo: ~37.0.3 => 37.0.12
react: ~16.9.0 => 16.9.0
react-dom: ~16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ~0.11.7 => 0.11.7
Expo Workflow: managed
You just saved my sanity - yes!
But I hadn’t figured out the pattern yet, so cheers!
@adamjnav - 3 ppl so far experiencing this on Expo, should we file a bug? I started experiencing this after the SDK 39 release but not I don’t think it’s tied to SDK 39.
Hi @aryk-
so… this seems to be happening to me randomly at this point. As I am months behind my release date, I have been a baaaad programmer & simply restarting
Have you figured this out yet?
No, I’m on the newest SDK of expo and it’s still happening with me…it’s very annoying.
@adamjnav - What other info do you need from us to look into this? Seems like 3-4 people here experiencing this and probably others as well. Would restarting my computer help…maybe “expo” needs a clean restart, maybe something is wrong in its cache?
There seems to be some kind of socket in use. I ran expo publish and then immediately restarted “expo start” and then it stopped the expo publish. Maybe this helps narrow things down:
Building iOS bundle
Finished building JavaScript bundle in 14508ms.
Building Android bundle
socket hang up
Error: socket hang up
at connResetException (internal/errors.js:612:14)
at Socket.socketOnEnd (_http_client.js:493:23)
at Socket.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1252:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Same here. I thought I was losing my mind
@lanman2000 - We are all losing our minds on this one…lol
What version of expo-cli are you using? Maybe we can pin it down to that?
3.27.13
Unfortunately no, has been happening to me since the 39 release… but probably related to newer versions of expo-cli idk.
@adamjnav - should we file an actual bug here…seems like it’s affecting a good number of people.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.