On my server I am using Chromedp (a Go package) that runs a headless version of chrome to generate PDFs for me.
When I run this process on my windows machine it works great. Then when I try to run it on my Amazon Linux AMI server I always get the error message "context cancelled"
I asked on their github page if that was an issue with something I was doing and I was told that it might be happening if the browser crashes or fails to start.
How can I verify that my version of chrome is working through the command line?
I followed this guide when I was installing chrome.
I can't debug my react native / expo app in WebStorm, but I can in Visual Studio Code.
I have a react native app that I can successfully run using expo. I set up the configuration according to the info on this site:
https://blog.jetbrains.com/webstorm/2018/02/webstorm-2018-1-eap-181-3263/#debugging-expo
When I click "run" or "debug" and "Debug JS Remotely" is turned off, the bundler builds a JS bundle and the app starts on my devices.
But once I turn on "Debug JS Remotely", the bundler only says:
Starting custom debugger by executing: : [my working directory] [my working directory again]
and never goes on to build the JS bundle.
After a short while, a red screen appears on the device, and it says:
Unable to connect with remote debugger
Timeout while connecting to remote debugger
onFailure
DevSupportManagerImpl.java:851
onFailure
WebsocketJavaScriptExecutor.java:83
run
WebsocketJavaScriptExecutor.java:142
handleCallback
Handler.java:790
dispatchMessage
Handler.java:99
...
The bundler doesn't say anything more than the message above.
As soon as I turn off remote debugging, the the bundler starts building again and finishes with
"Building JavaScript bundle: finished in ...ms"
as usual, but the device, again, shows the red screen with aforementioned messages, or doesn't show anything but the regular white screen with a message at the bottom saying "Downlading JavaScript bundle 100,00%". I either have to stop and restart within WebStorm or I have to close the expo app and re-open it. Either way will make the app start again on my device.
This is my first time working with javascript, react native, expo, so I am not sure, but it should be possible to debug in WebStorm directly, right? As mentioned, in Visual Studio Code everything including debugging works fine, so I don't think it's anything in the code. Maybe someone here has an idea where the problem lies?
node -v: v11.6.0
react-native -v: react-native-cli: 2.0.1, react-native: 0.57.1
Any help will be greatly appreciated! Thanks in advance!
PROOF
HOWTO
Looks like there's been an update to how you can setup Configurations since you tried.
Try changing the Bundler host to 127.0.0.1 and try again.
I just setup Webstorm v2020.2 yesterday to debug my Expo application and it is working as expected.
These instructions were all that I required: https://www.jetbrains.com/help/webstorm/react-native.html#ws_react_native_create_run_config
On the main menu, go to Run | Edit Configurations, click icons.general.add.svg and select React Native from the list. The Run/Debug Configuration: React Native opens.
Choose whether you want WebStorm to build and launch the application for you:
Select the Build and launch checkbox if you are launching your application for the first time or if you have updated its native code since the last run.
If your application uses Expo, clear the checkbox because this bundler takes care of the process itself.
If you selected the Build and launch checkbox, choose the target platform, Android or iOS. Depending on your choice, WebStorm will run the bundler with react-native run-ios or with react-native run-android.
Optionally, type the arguments to be passed to React Native, for example, specify the simulator type through the ‑‑simulator flag: ‑‑simulator="iPhone 4s".
In the Bundler host field, specify the host where the React Native bundler runs, the default value is localhost.
If you are using Expo, change the default bundler host to ensure successful connection with the debugger. This connection may fail because WebStorm by default uses localhost to start debugging while Expo expects 127.0.0.1 or an external IP address depending on what is selected in Connection field of the Metro bundler configuration. See Debugging a React Native application that uses Expo for details.
In the Bundler port field, specify the port on which the React Native bundler runs, by default 8081 is chosen, learn more from the React Native official website.
Choose the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.
Specify the path to react-native-cli and the working directory of the application. Optionally, type the environment variables for react-native run-android or react-native run-ios.
By default, WebStorm starts the React Native bundler automatically when you invoke the run/debug configuration. If you have already started the bundler from outside WebStorm, for example, from the command line, you can re-use it without stopping and restarting. Select your bundler in the Before Launch area and click Remove.
The issue is tracked at WEB-35719, please follow it for updates
I'm trying to use an older version of Firefox on AWS (running selenium, 55 isn't compatible) but I haven't had any luck. When I try to download the compressed older files, I get
(firefox:6186): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
Any ways to fix this/alternate ways to download?
I faced same issue with firefox when I was running selenium project with it. I did the following things that helped me. First uninstall the firefox by using command,
sudo apt-get remove --purge firefox
Some of the old files could also be there, you need to remove them manually.
Then you can install the previous version from the link provided below which shows list of all previous versions of the firefox, version 54, works fine for selenium.
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
When you install it, Mozilla build for Firefox would be opened as a browser and you can perform selenium tests there.
Hope this helps!
When trying to set up the Divio app, I get this warning screen.
DivioSetupWarningScreen
However, even though the picture claims I do, I don't have Docker Toolbox installed. When I try to install Docker for Windows on anyways by pressing the "Continue" button as seen in the picture above, I get this.
DockerNotInstalled
In the second picture, I tried clicking "Contact Support," but that led me to a blank webpage. Also, if I try to install Docker Windows without the Divio App, but it would not let me because I do not have the enterprise Windows OS, just the home. I also tried downloading Boot2Docker Start, but that didn't really help.
I'm at a loss as to what to try next. Any help would be appreciated.Thanks!
As you have Windows Home edition, one of the solutions would be to install Docker Toolbox/VirtualBox manually and use Divio CLI in PowerShell. Because current version of Divio App does not recognize Windows edition type. It should be presented in the next coming release.
I'm trying to get debugging to work on ff/chrome. I've checked all the post that come up when you google.
What I've done:
- setup a ff profile
- setup a in place deployment and double checked the remote urls..
- all plugins are enabled (including Javascript debugger)
As it seems the webstorm debugging extension was not installed in firefox (or chrome). I cannot find anything on how to get it installed. (I've allready tried re-installing Webstorm)
When I debug a file, firefox opens, but displays no page and the url-bar is empty..
I'm using Webstorm 4.0 and Firefox 11
Although this post might be outdated:
You need to install the JetBrains IDE extension in the corresponding browser.
When this is done, check if the same host and port are specified for Webstorm as well as for the extension as well.