expo: Cannot view app: ::ffff:127.0.0.1 "GET /debug HTTP/1.1" 404 18 "-" "-" Packager is not running at 192.168.1.26:19001
After upgrading to SDK 25 and running npm start I see the QR code in console, and every 100ms the following message gets output to console:
19:01:04: ::ffff:127.0.0.1 - - [24/Jan/2018:12:01:04 +0000] "GET /debug HTTP/1.1" 404 18 "-" "-"
When trying to open the app on the phone it doesn’t load with error
Packager is not running at 192.168.1.26:19001
Any Ideas what’s wrong here?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 30 (8 by maintainers)
fantastic. can you all try updating react-native-scripts to the latest, please? 1.11.1
Hmm, that didn’t work for the repeating 404 to /debug for me.
Still same
I think the issue is related to react-native-scripts. I have been running the packager using
npm start, which in turn runsreact-native-scripts start. When I tried the running the packager usingexp startinstead, the problem is gone.@fozzylyon when client on the phone isn’t latest, it says the version is unsupported, but I have the latest client and the error is different. Also, the message gets printed right after project gets compiled, even before I try to view it on device/simulator.
I’ve already did it
npm i -D react-native-scripts@latest(1.11.1);exp build:androiderror fixed by upgrading to the latestnpm install -g exp@lastest::ffff:127.0.0.1 - - [18/Nov/2018:15:59:26 +0000] “GET /onchange HTTP/1.1” - - “-” “okhttp/3.11.0” updating to the latest version of react-native-scripts did not work for me. The app is a brand new app created with react-native init command with the navigation module added to play with the createDrawer navigation function.
Versions: node: 8.11.3 react-native-cli: 2.0.1 react-native: 0.57.5 win-10: 10.0.17744 N/A Build 17744
Questions where is the scripts.js found and is it removed when installing the new version 2.0.1, now I have a new module on the devDependencies object in package.json
I’ve updated to react-native-scripts@1.11.1 and exp@50.0.1 and am still having this problem.