I'm simply trying to run some of the tests in the example folder under Integration and it will not run on Chrome. Runs on Electron and Edge but refuses to run on Chrome and throwing the attached error after unsuccessfully trying.
My version of Chrome is Version 86.0.4240.111 (Official Build) (64-bit)
Current Cypress version is - cypress": "^5.5.0
I reinstalled Google Chrome and it started working. Simple as that.
I just saw this issue on mac and I just had to hard quite Chrome and relaunch it. I didn't have to uninstall and reinstall it.
This issue comes when there is something wrong with your localhost configurations. Please check etc/hosts file.
You can refer to this link for further clarifications.
Related
I know this message has been already asked before but none of the answers has fixed my issue,
The error message:
I have already tried disabling the hotspot of my emulator (which is a Pixel XL API 30) but it doesn't work. I have also tried restarting my pc, IDE and emulator and also changing my IDE from vs code to Android Studio but the error doesn't go away. I am new to flutter and I don't want to give up at the start!
Disable your mobile hotspot. If you use windows 11 that was my error try, will run normally easy like this.
For me, it was the Windows Hotspot Wifi as "#Salah dine Maham" said.
As I know it is related to a gradle issue (shows up from about gradle v6.3), I went to the
android/gradle/wrapper/gradle-wrapper.properties
I updated the distributionURL into :
distributionUrl=https\://services.gradle.org/distributions/gradle-7.1.1-all.zip
You "may" need to update the gradle plugin on the android project.
And now you can debug again freely through Windows Hotspot wifi.
So, as I said I couldn't find any solutions but here it is:
delete ANY VMware processes or, if you can, unistall VMware and use virtualbox instead, even if vmware is not running it will confict with other emulators.
Credits
When I try and run debug I get an error saying something like "Error connecting to the service protocol: HttpException"
How do I fix this issue so I can debug?
EDIT: I am on a windows computer.
You may find this helpful where someone had a similar issue and managed to fix it by putting NO_PROXY=localhost,127.0.0.1 in their .bash_profile and then restarting their terminal.
It seems that it is an issue with Android Q itself and I have downgraded to Android Pie and debugging now works, if you have issues try downgrading to Android Pie API level 28 if using Android Emulation.
I am using protractor#3.2.2. It was working fine with chrome all these days. But all of a sudden it is not able to connect to chrome(chromeDriver).
It says
SessionNotCreatedError: session not created exception
It is able to connect to Firefox and Edge.
I am using chromeDriver#2.21
Any ideas about how to fix it?
The chromeDriver 2.21 supports till chrome version 53, But i was using chrome version 54. This is the reason why the chromeDriver is not able to connect to chrome.
Once i downgrade to chrome version 53, everything started to work as expected.
So if you guys face the same issue, check your chromeDriver version and your chrome version.
im gettting this report on the console while I'm trying to run the app on eclipse kepler, and the emulator doesn't open, any idea whats wrong or any advice to fix it ?
[2015-01-05 17:53:02 - Emulator] NAND: bad arg: 14/adt-bundle-mac-x86_64-20130917/sdk/platforms/android-10/images//system.img
i just uninstall the andorid sdk, and then i restart eclipse and i got it working again.
i think the problem was : it was needing to update to the latest sdk tools.
I'm using Eclipse to develop an Android application, and I want to use Bluestacks as my emulator. I tried adb 127.0.0.1 successfully. When I double click my project's APK, it says that my app has been installed, but when I try to run it in Bluestacks my app store it says "device could not find your app". Alternatively I also tried to run it by using Eclipse IDE, and it said "An established connection was aborted by the software in your host machine". How do I fix this?
Try restarting Bluestacks and following the procedure again. By following the procedure I mean running the command adb connect 127.0.0.1 and reinstalling the APK you want to test. It worked for me.