I followed all the installation instructions listed on expo’s website but I can’t even get the server running.
When I run expo start,
“Starting project at /home/rnprototype”
is printed on the terminal and that’s all. It hangs and stays like that forever. No useful message to even help in debugging.
Its really frustrating, i’ve reinstalled expo-cli, node and even my OS but the same thing keeps happening.
I would really appreciate if someone could help me out with this or even point to a log file where I can start debugging from.
Output of expo diagnostics
Expo CLI 3.21.5 environment info:
System:
OS: Linux 4.4 Ubuntu 18.04.4 LTS (Bionic Beaver)
Shell: 4.4.20 - /bin/bash
Binaries:
Node: 12.18.0 - ~/.nvm/versions/node/v12.18.0/bin/node
npm: 6.14.4 - ~/.nvm/versions/node/v12.18.0/bin/npm
npmPackages:
expo: ~37.0.3 => 37.0.12
react: ~16.9.0 => 16.9.0
react-dom: ~16.9.0 => 16.9.0
react-native: ~0.61.5 => 0.61.5
react-native-web: ~0.11.7 => 0.11.7
npmGlobalPackages:
expo-cli: 3.21.5
Managed to get past this.
I had to edit my hosts file.
opened 11:13PM - 16 Nov 19 UTC
closed 01:10PM - 12 Jan 20 UTC
## Description
For the past couple of days since trying to update the expo-cl… i from version 3.0.4 to 3.4.1, when I try running `expo start` the dev tools opens on port :19002 in the browser, as expected but when I try to launch the app using the ios or android simulators, it hangs and terminal eventually publishes an error saying that it cannot find an open port, I have tried rolling back to a different version of expo-cli and have tried multiple versions of node, but nothing will get past this error
## Expected Behavior
freeport-async to find a port, connect and launch the expo app
## Observed Behavior
The simulator loads with the 'There was a problem loading the requested app' screen. When i test freeport-async in a separate repo with the following code
```
const freeportAsync = require('freeport-async');
freeportAsync(19000).then(port => {
console.log(port);
});
```
I get assigned the port I pass in to function
Below is the error message terminal will show after 15 seconds waiting on expo start
```
(node:4996) UnhandledPromiseRejectionWarning: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received 65536.
at Server.listen (net.js:1412:13)
at /Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:8:12
at new Promise (<anonymous>)
at testPortAsync (/Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:6:10)
at availableAsync (/Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:24:17)
at Promise (/Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:37:23)
at new Promise (<anonymous>)
at freePortRangeAsync (/Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:33:10)
at /Users/Dave/.config/yarn/global/node_modules/@expo/xdl/node_modules/freeport-async/index.js:43:18
(node:4996) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:4996) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
```
## Environment
Expo CLI 3.0.4 environment info:
System:
OS: macOS High Sierra 10.13.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.13.0 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.2 AI-181.5540.7.32.5056338
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
@storybook/react: 5.2.1 => 5.2.1
@types/expo: ^32.0.13 => 32.0.13
@types/react: ^16.8.25 => 16.9.11
@types/react-native: ^0.60.3 => 0.60.22
expo: ^35.0.0 => 35.0.1
react: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
npmGlobalPackages:
expo-cli: 3.0.4
Also specify:
ios simulator 10.1
## Reproducible Demo
This happens with expo init and a blank project.