For the last 24 hours I have been trying to get my expo client to build JavaScript on my device. I have been using expo for some weeks now. And thou it may be difficult to get it running I some how manage to use it for some hours. Usually I can easily connect using tunnel. Recently I was able to 'trick it' to work without internet. But for the last 24 hours I can't get to work using any of the options available... I have scout the Internet for solutions and tried them with no success .
I keep getting type error java.net sockettimeoutexception network timeout error .....1000ms I have had to reset a lot on my system disabled all firewalls. Pause antivirus , reset react native packager hostname, clear cache for both expo and npm etc..
Lastly I tried removing and downloading the expo client app . But the app fails to download. Tried other apps and they work OK..
Finally got it to install after rebooting several times
Related
I'm very new to React Native and I'm understanding now Ports and similar things. In the last days I was able to access through Expo Go my app, but starting from today I ran into issues.
I think the problem was, that I was accessing the app using an university wi-fi connection, while the other days I used a mobile data connection. With Wi-Fi I was not able to access the app. The error log said: java.net.connectException: failed to connect to (...)
So I started a big journey thorugh ports, ip addresses and firewall, arriving to the ubuntu's ufw. Actually I don't know exactly what I've done, but the last try was to disable everything (like it was at the beginning) and retrying to access the app, nothing changed. The error log was: java.net.SocketTimoutException: failed to connect to (...) from (...)
I tried also use tunnel (like this question says Unable to connect to Expo React Native Project on WSL2 with Expo Go on phone) but it didn't help. In this case, the app says New update avalable: downloading... but never ends.
So, any suggestion to understand a) which is the real problem (a part that I've done something that I didn't understand) and b) how to solve it ?
I know this is a kinda weird question, but I couldn't find any relevant info about this issue elsewhere so I took the easier way and wrote here.
My problem seems to be related only to my PC, that I cant access npmjs.com, I have no clue why. When I try accessing the npmjs.com website it tells me that Cloudflare errored with error 1034 ( Edge IP Restricted )
Cloudflare error image
This does not happen when accessing docs.npmjs.com, that works just fine. The other part of the problem is that not even npm CLI is working, when I try to npx or install something it errors with E403 - Forbidden.
npm CLI E403 image
As I said previously this only happens on my PC, elsewhere on my network this does not happen.
I have a desktop PC connected with a cable to my router, but when I check with my work laptop on wifi, everything is working as it should be.
I tried connecting it straight to the modem, but that does the same so I isolated it to be an issue on my PC only.
This issue has been happening since yesterday when I found out after coming back to node.js after some time.
Just in case it could be related, I'm using a pi-hole with OpenDNS settings ( Had an unused raspberry pi, so I followed tutorial on youtube on how to get it working ).
To this day I haven't had a single problem with it, I've been using it for over a year now.
Thank you for reading and potentially answering my question.
I encounter an ETIMEDOUT error whenever I try to use the gatsby-source-shopify to build a gatsby site connected to my Shopify store.
With a small store, this works perfectly but with a large store like the clients I'm working with that has over 1000 products, it shows a timed out error, both during development and when deployed to Netlify.
My issue is similar to that at this github issue but I have tried all the suggested and still face the same issue.
I'm working on a React Native app, testing in an android emulator. I've used the standalone React Native Debugger app as well as the debugger that opens in Chrome. In the Chrome window, the Network tab shows no activity, so that's no help. In the standalone debugger, the same is true until you right-click and choose Enable Network Inspect. The problem I'm having is that after I enable network inspecting in the debugger, all network requests fail - the inspector shows their status going from Pending to Canceled after a few seconds. I can see in my server logs that no requests are coming in. It's like debugger itself is somehow blocking the requests.
I've set up adb to run as root. When I run react-native run-android the output includes Running adb -s emulator-5554 reverse tcp:8081 tcp:8081, so I think things are starting up fine. The network requests from the app (login etc.) work fine (a typical URL would be http://10.0.2.2:2080/api/LoginScreenController/GetIdentityStatus), until I choose "enable network inspect" in the debugger, at which point all network requests fail as described above.
Any suggestions would be appreciated.
I know that I'm too late but perhaps it will save time for somebody.
During the update of the react-native, I did update the version of the react-native-reanimated from v1 => v2, and after it, I faced the same behavior.
Version 2 requires to enable Hermes engine if it won't be enabled then all the requests will be in pending status
When trying to run exp start --tunnel in a react-native project, I often see the warning:
22:15:31 [exp] Your URL is: exp://192.168.200.83:19000
....
22:15:31 [exp] Switched to a LAN URL because the tunnel appears to be down. Only devices in the same network can access the app. Restart with exp start --tunnel to try reconnecting.
This is a problem since none of my devices or the AVD can connect to this URL to download the project.
The problem does not seem to related to any firewall settings as it does not occur every time (just very consistently). When the error does not happen, I get a URL that I can work with that looks like:
22:44:38 [exp] Your URL is: exp://en-ux3.myexpousername.myapp.exp.direct:80
Is there something that can be done about this to get it to stop switching? What causes this switching exactly? Is there some way to get devices to be able to use this URL instead (I have an android device connected to same wifi, but seems to be unable to download the project from the LAN URL)?
** Totally new to react-native and expo, so if I am missing evidence of any common debugging steps for this kind of problem, please let me know what they may be in the comments so I can update the question.
UPDATE:
A similar question to this is addressed in the expo forums: https://forums.expo.io/t/switched-to-a-lan-url-because-the-tunnel-appears-to-be-down-only-devices-in-the-same-network-can-access-the-app-you-can-restart-the-project-to-try-reconnecting/4483.
I was having the message
Switched to a LAN URL because the tunnel appears to be down. Only devices in the same network can access the app. You can restart the project to try reconnecting.
And I've solved it closing Visual Studio (then pressing the Restart button from Expo XDE)