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.
I was working on one poc which will connect to salesforce account . The mule version is 6.3.2 and sales force version is 6.3.2. Till 2 [![enter image description here][1]][1]days back it was working fine.
I came to know that last weekend sales force as done TLS upgrade to 1.1 from 1.0. When i was testing my flow getting the below exception:
Root Exception stack trace:
[UnexpectedErrorFault [ApiFault exceptionCode='UNSUPPORTED_CLIENT'
exceptionMessage='TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https.'
]
]
When i saw the mule documentation it says that sales force connector 7.1.2 as addressed this issue and I update my connector in studio and retried the scenario which is not working.
Can some one help me out on this.
Regards
Vikram
I previously had to set the following property in the application settings:
https.protocols=TLSv1.1,TLSv1.2
And -Dhttps.protocols=TLSv1.1,TLSv1.2 in my wrapper.conf for Mule standalone.
You can put your configuration in tls-default.conf in MULE_ESB/conf/ folder
and then put the value inside like below:
enabledProtocols=TLSv1.1, TLSv1.2
enabledCipherSuites=TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_RC4_128_SHA, SSL_DH_anon_WITH_DES_CBC_SHA
Or if you want to test from your anypoint studio, just create the tls-default.conf and put under your resources folder
Another information I can add is try to input your url destination to https://www.ssllabs.com/ssltest/ to make sure the TLSv1.1 is enabled by your endpoint or the chiper suite enable too
Similar is answered in https://forums.mulesoft.com/questions/41012/getting-error-when-hitting-a-rest-api-via-https.html#answer-43960
Below is the answer I posted.
I resolved it in my system.
When it is not working in the Runtime that is attached in the Anypoint
studio then follow the below steps.
Navigate to the Anypoint studio installation directory
Search for "tls-default.conf" in the folder. This will show you all the files for all the Runtimes that you have installed.
there will be a property "enabledProtocols" make sure that it contains the TLSv1 in it as below
enabledProtocols=TLSv1,TLSv1.1,TLSv1.2
This above should apply to Cloud hub (Most of the times it is already
enabled) or on-premise systems.
Salesforce are now disabling TLS 1.0, forcing TLS 1.1 or higher.
For Java versions >= 1.8 this is not a problem, but for earlier releases you will want to set the SSLContext. This solution worked for me:
if (Double.parseDouble(Runtime.class.getPackage().getSpecificationVersion()) <= 1.7) // Java versions > 1.7 are compatible with TLS 1.1 or higher by default - we want TLSv1.2 for our needs
setSSLContext(SSLContext.getInstance(SSL_VERSION_TO_USE_FOR_SALESFORCE_LOGIN));
private static void setSSLContext(SSLContext context) {
SSLContext.setDefault(context);
try {
/* Either of the first two parameters may be null in which case the installed security providers will be searched for the highest priority implementation of the appropriate factory.
Likewise, the secure random parameter may be null in which case the default implementation will be used. */
context.init(null, null, null);
} catch (KeyManagementException e) {
// handle exception
}
}
Navigate to Setup
In the Quick Find bar, type in Critical Updates
Select Critical Updates
Locate the Require TLS 1.1 or higher for HTTPS connections​ under the Update Name column
Click on Deactivate.
I'm on a Mac and I've installed the latest version of the App Engine PHP SDK (1.9.19 - 2015-04-13) which include support for XDebug (since 1.9.18).
I'm using the latest version of PHPStorm (8.0.3) with the GAE plugin.
I've no trouble to run my app through PHPStorm but I can't get the debugger working automatically (will explain what it means few lines below).
Each time I try to debug my app, the debugger pane stays saying "Waiting for incoming connection with ide key '11634' " (the ide key is always a random number).
No breakpoints are triggered, and when I stop the execution, a little red popup displays: "debug connection with xdebug was not established"...
I've tried what the Google documentation suggests and it didn't work either.
Finally after hours of trying almost anything (compiling my own version of XDebug, checking every conf file, overriding php.ini to ensure paths to XDebug is correct and XDebug is on, etc...) I found a "workaround"...
The only way I can't get the debugger to work is to launch the app, then go to the debugger pane to know what's the key it's waiting for (let's say "15981"), then go to my web browser and manually add XDEBUG_SESSION_START=15981 as parameter to the URL.
Since the key changed every run, it's really a pain to work like that, and I don't talk about page redirection, etc...
Is anyone having a thought on that?
Thanks
You can start local App Endine server with App Engine For PHP run configuration, just as in JetBrains tutorial.
Then please enable Listen to incoming connections (that phone with small bug on toolbar near run configurations, or in menu Run | Start Listening for PHP Debug Connections). Then reload the page in browser. Debugger should stop on the first breakpoint or on the first line of code if that setting is enabled.
Also feel free to watch or vote the issue on bugtracker.
#leneshka has the answer! I've been pulling my hair out trying to figure out how to get PHPStorm to use the xdebug.idekey value I specified in xdebug.ini.
As soon as I enabled Start Listening for PHP Debug Connections, I was able to start debugging with my personal xdebug.idekey value.
So far, I have been working on version 1 of my server application. I could reach the application at
https://myappid.appspot.com
using my browser. (Note: I am using https, not http)
Now, I am changing the the version id to 2 (version 1 is now production, version 2 is next gen release and I would like to test that). I need version 1 to remain the default version for the users are using the stable, production version.
Now that I have 2 versions, I tried to reach version 2 static front page from by browser (Chrome) using
https://2.latest.myappid.appspot.com
as per the instructions I could find. Instead chrome gives me the following error
*You attempted to reach 2.latest.myappid.appspot.com, but instead you actually reached a server identifying itself as .appspot.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of 2.latest.myappid.appspot.com.
You cannot proceed because the website operator has requested heightened security for this domain.
This problem goes away for http://2.latest.myappid.appspot.com
I have requested secure connection through web.xml's
<transport- guarantee> element. So, what am I missing?
Try 2.myappid.appspot.com.
Also, in the Admin Console when you click on Versions, you can see all versions of your app. A number of each version is a link - you can click on it to get access to that version running.
If you try to access the new version using https, you should use the following instead:
https://2-dot-myappid.appspot.com/
Do you need 2 live versions of the same app?
Although possible with some limitations, this is not what the system was designed to do. The https is apparently one of these limitations.
If you want version 2 to replace version 1, than all you need to do is "set default" on version 2, and than it will be the one mapped to https://myappid.appspot.com