Something went wrong.
Packager is not running at 192.168..:80
for the above error i have tried to allow ufw to port 80 . After that i got the same error but the port value was 19001 . I did allow 19001 port with ufw but it didn’t help me to resolve the problem.
The error that comes in the web browser when i run it in the web are:
Unhandled Rejection (TypeError): expo__WEBPACK_IMPORTED_MODULE_15__.Permissions is null
According to me these error may occur as i have not given any permission through my android device. Correct me If I am wrong.
The SDK version specified in that app.json is pretty old. Also it should not be looking for the packager on port 80. Another thing is that it’s not set up for Expo Web.
Maybe see what happens if you run expo upgrade with a recent version of expo-cli.
If that doesn’t work, I think it would probably be best to create a new Expo app with expo init and then either compare the differences between the two, or else copy files from the cloned repo to your new app.
And you get a line printed out showing what port Metro is listening on (usually 19001)?
$ expo start
Starting project at /tmp/test
Expo DevTools is running at http://localhost:19002
Press d to open DevTools now, or shift-d to always open it automatically.
Starting Metro Bundler on port 19001. <===
Tunnel ready.
exp://192.168.18.4:19000
$ expo start
Starting project at /home/shiraz/img
Expo DevTools is running at http://localhost:19002
Press d to open DevTools now, or shift-d to always open it automatically.
Starting Metro Bundler on port 19001.
Successfully ran adb reverse. Localhost URLs should work on the connected Android device.
jq is a tool for processing JSON inputs, applying the
given filter to its JSON text inputs and producing the
filter's results as JSON on standard output.
The simplest filter is ., which is the identity filter,
copying jq's input to its output unmodified (except for
formatting).
For more advanced filters see the jq(1) manpage ("man jq")
and/or https://stedolan.github.io/jq
Some of the options include:
-c compact instead of pretty-printed output;
-n use `null` as the single input value;
-e set the exit status code based on the output;
-s read (slurp) all inputs into an array; apply filter to it;
-r output raw strings, not JSON texts;
-R read raw strings, not JSON texts;
-C colorize JSON;
-M monochrome (don't colorize JSON);
-S sort keys of objects on output;
--tab use tabs for indentation;
--arg a v set variable $a to value <v>;
--argjson a v set variable $a to JSON value <v>;
--slurpfile a f set variable $a to an array of JSON texts read from <f>;
See the manpage for more options.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 961 100 961 0 0 7171 0 --:–:-- --:–:-- --:–:-- 7171
(23) Failed writing body
I am killing the experience using CTRL+C command and clearing recent opened app in expo app at client side i.e on my android device.
Correct me If I am doing anything wrong.
I am trying to load the app in the expo client installed on my android device by pressing ‘a’ in development mode in the terminal.
It needs to be “jq .”, not just “jq”. Anyway, jq . just formats the JSON nicely, so it’s not absolutely necessary id you just want to check what ports are mentioned in the JSON.
When you open an app within the Expo client it’s called an experience, because it’s not a standalone app. On Android it still shows up as two separate entries in the list of recently opened apps. What I meant was you should swipe both of them away in the recently opened apps list on your phone.
Ah, OK, well that should work, although I haven’t used that other than on the Android emulator a few times. What I do is either scan the QR code or choose it from the “RECENTLY IN DEVELOPMENT” list in the Expo app.
I made the new project in different directory using expo init, then i run it using expo start ,the new project worked fine but after some time same error appeared on the screen.
If you do the same test to check the ports in the manifest, does it also show port 80? If not, maybe you just need to restart the Expo app again. I know it can sometimes get into a state where it thinks it should connect to port 80 instead of the usual port 19000.
The packager for Expo Web is Webpack rather than Metro Bundler, so that probably explains why one would be working when the other isn’t.
OK, I’ve got a little more info. If I manually kill the Metro bundler process, the dev server suddenly switches to advertising port 80 instead of the port that Metro was listening on.
So my suspicion is that Metro is dying on your machine for some reason.
I’m not entirely sure how to debug that, but maybe try running expo like this and see if it gives you any more info in the terminal when this happens:
