I've created an expo app with exp init MyApp command and started it by running exp start in MyApp directory.
Then I'm scanning barcode which was printed in console with expo mobile app on android device.
Then "Something went wrong" screen is rendered instead of the app.
View log shows "Uncaught Error: Couldn't load exp://.....".
No errors in expo packager console output.
It used to work sometimes ago.
What solved this for me was simply changing the connection from LAN to Tunnel. When you start an expo app, a browser window will open with a URL like http://localhost:19002/.
Along the left side is a Connection option set to LAN by default. Changing it to Tunnel before scanning the QR code with the expo app solved it.
For me the problem was happening when running over WiFi, as the tools always use the your first connection (you can check it by running ipconfig) and my first connection was internet.
If that's you case you may try this workaround for changing you connections priority:
Go to Control Panel > Network and Internet > Network Connections
Right click the desired connection (Higher Priority Connection)
Click Properties > Internet Protocol Version 4
Click Properties > Advanced
Uncheck 'Automatic Metric'
Enter 10 in 'Interface Metric'
Click OK
In my case, the issue was fixed by doing the following on my Android (Galaxy Note 5):
Go to Settings > Apps > Application Manager > Expo
Scroll down to Draw over other apps and toggle it off and then on again
Close out of everything, re-open expo, and try connecting
It still threw an issue once before working perfectly upon further tries.
For my case, using wireless adapter, I had to make my Network profile private.
1) Go to Properties of wireless network
2) Make network profile private
It was needed to reset "Draw over other apps" permission for Expo mobile app.
How that is fixed on Android 6.
Settings->Apps, press "gear", find "Draw over other apps" item and select it. Find "Expo" app, select it. Enable "Permit drawing over other apps" option in case it is disabled. Otherwise, disable and enable it again.
Make sure that you are using the same wireless network for iOS or Android phone as your computer.
In my case, I had "host" set to 'localhost' in the XDE - which of course won't work on my physical device ;-) So, if you want to debug on a physical device, make sure your host is set to LAN instead. (Tunnel would work too, but would make debugging painstakingly slow)
For me its worked by selecting the tunnel connection rather than LAN in metrol Bundler..
Try it out....
In my case, expo app was outdated. I just updated expo from store and it started working.
In my case, it works when I changed connection LAN to Local.
but it requires to connect phone through the data cable.
If you have a similar issue but the error says 'Uncought Error: java.lang.Exception: No launchable update', make sure you remove the "runtimeVersion" from your app.json while developing. Strangely enough, having "runtimeVersion" present works on iOS but it will fail to run on Android Expo Go app.
I had the same problem and I solved it by deactivating the Virtualbox internet connection, that happens because Node take that connection to start the packager.
Control Panel -> Network and Internet -> Network Connections
In my case is "Virtual Box Host-Only Network"
Right clic on that, and Deactivate
For anyone that using ESET firewall, you have to go into firewall rules and allow ports 19000,19001,19002, Advanced->Rules->Edit, on General tab select Direction->Both, Action->Allow, then visit Local tab and on port field add the mentioned ports above, click ok. Do this action for every port you need to add.
In my case, the problem was not with the firewall the problem was with my internet I was running my computer and phone on two different internets then I connected my phone to the router which is connected to my computer and again I tried it worked
I had the same problem and fixed it on Windows 10 by making my machine discoverable on the network:
Click wifi icon in app drawer.
Go to the list of wifi connections and click your connection.
Click "Properties". This opens up the page associated with your connection.
Under "Make this PC discoverable", turn the slider to "On".
For macOS users and if you are running over Wi-Fi:
Choose Apple menu > System Preferences, then click Network
Click Wi-Fi in the list at the left, then click Advanced
Find the network you are connected to
Then drag it to the top of the preferred networks list to give highest priority
This procedure solved my problem.
For me, expo wasn't started. So expo start in VS Code terminal solved it.
It depends on what OS are you using. If it is Windows 8 or earlier, try updating the version. In Windows 10 and Windows 11 it should work correctly. Try installing expo globally instead of local install.
You should also install expo in the project root directory after project setup:
npm i expo // or npm i -g expo for global installation
If you are using yarn, then try npm as well.
According to me, what have solved my issue were a few things below:
Restart Expo and then try scanning the barcode once again.
You can also reload the application by clicking R on Code editor. And the caption "Something went Wrong" will reload.
You can check the internet of your mobile device and the laptop/desktop is connected with same network.
Restarting the project sometimes also helped me. As the file does not compile properly it sometime create this issue.
Hope this you will your issue resolved soon.
I believe this issue is happening due to mismatch version of your AVD and your expo mobile application. I created new AVD with newer version of Nexus 6 API and issue was resolved. I also needed to reset "Draw over other apps" permission for Expo mobile app.
For me, I have to close and kill expo (from RAM) AND close the QR Code overlay view to get it work on Android 5.1.1.
Sometimes I have to wait a few minutes or I get a camera view and a text above about scanning the QR Code (but without a scanner over the camera view).
If you're not able to load the http URL in your phone's web browser, try using the tethering/mobile hotspot feature on your phone (beware of data usage, though), connecting your computer to that WiFi network, and restarting the packager. If you are using a VPN you may need to disable it.
I solved it by deactivating it, although you could also open port 19000, which is used by Expo.
Uninstalling and reinstalling expo on my Mac cleared this for me. Expo was complaining about being out of date.
Do some things.
ForceStop App.
Restart App.
Clean Cache and Clear Data.
Else due to outdated expo. Update expo from play store.
Note: Expo no longer available for IOS physical devices.
Let me know if any issue occurred!
In my case was that the phone was connected to a VPN (CyberGhost) and it showed up only a white screen D:
In my case, windows firewall was blocking it. So, I made it run by turning the firewall off.
I think that the solution for this might be the most simplest thing. What works for me when the app doesn't load on the emulator using expo is just clicking X and closing the info alert that pops up. You'll see the following Info Alert and if you close that out and try hitting the running on Android button again, then it should work. Otherwise deleting and creating a new virtual device also helps incase the cache or expo installation on the device is really causing problems.
That issue was solved very easily following these steps:
Sign in with the expo mobile app using your expo account.
When we run the app using the expo start command can see the localhost web page, In that web page left side can see Connection, by default it is Land,
change it to the Tunnel.
Scan the QR code.
Local connection works for me.
prerequisite :
Add the adb.exe path to environment variables.
(In my case : D:\AppDevTools\Android\Sdk\platform-tools)
Connect your android mobile phone to your pc using a USB cable.
Enable USB debugging on your mobile phone.
Note:
I have googled, and read these issues:
Cannot access API explorer on localhost
How to force loading dynamic, insecure content in Chrome?
and many others but they do not solve my problem.
The problem:
I'm running MacOS and doing my development int Debian VM running in Paralells.
I start up the dev server using the following command:
dev_appserver.py --clear_datastore --host 0.0.0.0 --admin_host 0.0.0.0 app
and I can access the app, endpoints, admin module etc from MacOS using my Debian machine IP eg. http://10.211.55.6:8080/_ah/api/my-service/v1/api etc... everything works fine and as expected except for Google API Explorer.
When I try to access http://10.211.55.6:8080/_ah/api/explorer I am redirected to http://apis-explorer.appspot.com/apis-explorer/?base=http:///10.211.55.6:8080/_ah/api#p/ as expected and I get the ssl error as described in the issue above (again as expected) but then I get redirected a couple of more times and end up at https://apis-explorer.appspot.com/apis-explorer/#p/
Note: I cannot click on the lock icon in the title bar because of the redirects
I've tried almost everything I can think of and have google extensively to no avail. Hope someone can help me, I suspect it has something to do with the dev server being run inside of a VM, but I am not sure.
there is a shield icon in the rightmost part of the address bar that appears when you access the api_explorer locally in chrome. Click and then select load unsafe script and it will load all the service endpoints you define.loading api_explorer locally
I am using openCyc and I am trying to connect to an image of a Cyc KB. I can browse this image on my browser (using chrome) and can successfully ping the address from the command line.
Now, when I try to create a new CycAccess("server", "port) the correct server and port of the image I am browsing on the browser I get an error saying connection refused which is printed out to the terminal.
For the server, it is simply xxxxx.yyyyy.com and the port is just for example 6622. Am I formatting this wrong or something?
Why would this happen?
Thank you,
Rich
I found out the answer to my question. IDK if this well help anyone else so I am going to post it.
Answer:
The port that you typically access a CYC Image through the browser is not necessarily the port that you will access it through the OpenCyc API. When I changed the port, it solved my problem.
Rich