I have
npm install -g create-react-native-appcreate-react-native-app AwesomeProject
cd AwesomeProject
npm start
I
This is taking much longer than it should. You might want to check your interenet connection
How can i solve this problem?
I am stuck in development.
you need to be on the same wifi network and that wifi network cannot be a public network (eg: restaurant, cafe, school) that is behind a NAT. if this is the case then you will have to use a simulator
i am on the same wifi network, and it is not a public one. it is my private house wifi
copy the url to your phone and open it in safari or chrome, let me know what you see
@brentvatne i tried to open the url on safari (eliminating the prefix exp://) : the browser gets no response back (message : "safari cannot open the page cause the server stopped answering")
Do you think is there any firewall setting on the house router, blocking that port?
thanks a lot in advance
I tried to use the iphone as hotspot, connecting my windows pc to it, but i got the same problem.
edit
_looks like it's the firewall installed on the machine, in my case ZoneAlarm.
I have disabled it and now i do not receive that error message.
Still i cannot see my project but this is may due to other problems.
As soon as i will have the enviroment working, i will post here the steps i did to get the result.
Thanks_
thanks for the followup @RomanSurface! i'd also recommend updating the version of react-native-scripts in your project -- npm i [email protected] --save -- this fixes a small bug (that may or may not impact you) with loading projects that have spaces in the project path
I m having the same problem, turned off firewall and done all troubleshotting but still project is not opening in expo app
@Azambadar I faced the same problem. Turns out I was creating a "LAN" connection on the desktop expo server. Switching to "Tunnel" solved it for me
Hi @manu-dikzit , my wifi connection was not supporting expo and expo worked fine with mobile phone hotspot.
same problem can't able to open
Most helpful comment
@Azambadar I faced the same problem. Turns out I was creating a "LAN" connection on the desktop expo server. Switching to "Tunnel" solved it for me