RequestError: Error: connect ECONNREFUSED 172.217.23.16:443Īt new RequestError (C:\Users\dbown\AppData\Roaming\npm\node_modules\appium\node_modules\request-promise-core\lib\errors.js:14:15)Īt (C:\Users\dbown\AppData\Roaming\npm\node_modules\appium\node_modules\request-promise-core\lib\plumbing.js:87:29)Īt Request.RP$callback (C:\Users\dbown\AppData\Roaming\npm\node_modules\appium\node_modules\request-promise-core\lib\plumbing.js:46:31)Īt self.callback (C:\Users\dbown\AppData\Roaming\npm\node_modules\appium\node_modules\request\request.js:185:22)Īt Request.onRequestError (C:\Users\dbown\AppData\Roaming\npm\node_modules\appium\node_modules\request\request.js:877:8)Īt TLSSocket.socketErrorListener (_http_client.js:392:9)Īt emitErrorNT (internal/streams/destroy.js:82:8)Īt emitErrorAndCloseNT (internal/streams/destroy.js:50:3)Īt process._tickCallback (internal/process/next_tick.js:63:19)
Info Chromedriver Install Opening temp file to write chromedriver_win32 to… Info Chromedriver Install Installing Chromedriver version ‘2.38’ for platform ‘win’ and architecture ‘32’ The error I get (full details) from npm install -g is: Npm config set chromedriver_filepath=C:\Users\dbown\AppData\Roaming\Chromedriver/chromedriver_win32.zip I also tried downloading chromedriver from the web and then pointing npm config at it (npm install chromedriver -chromedriver_filepath=C:\Users\dbown\AppData\Roaming\Chromedriver/chromedriver_win32.zip I also at one time used an alternative chromedriver url (npm config set chromedriver_cdnurl=). I edited NPM config to include proxy settings, both http and https. _ info Chromedriver Install Downloading …
I’m unable to use NPM to download Appium (npm install -g due to ChromeDriver failure:
Hi unsure how to install ‘Appium’ from source code, since that seems the only option in Git repository, whereas the Desktop version includes an exe download (excluding NPM). Original error: Error: read ECONNRESETĪt mand (C:\Program Files (x86)\Appium\resources\app\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:236:13))Īt .(oovy:36)Īt .stepFailed(oovy:40)Īt .runKeyword(oovy:23)Īt .startApplication(oovy:51)Īt .execute(oovy:40)Īt .(oovy:53)Īt .(oovy:74)Īt .$startApplication.call(Unknown Source)Īt TC01_Verify Correct Alarm n(TC01_Verify Correct Alarm Message:25)Īt .(ScriptEngine.java:194)Īt .(ScriptEngine.java:119)Īt .(TestCaseExecutor.java:328)Īt .(TestCaseExecutor.java:319)Īt .(TestCaseExecutor.java:298)Īt .(TestCaseExecutor.java:290)Īt .(TestCaseExecutor.java:224)Īt .(TestCaseMain.java:106)Īt .(TestCaseMain.java:97)Īt .main.TestCaseMain$runTestCase$0.call(Unknown Source)Īt n(oovy:22) Original error: Could not proxy command to remote server. Remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command.
Test Cases/TC01_Verify Correct Alarm Message FAILED.Ĭom.StepFailedException: Unable to start app at: ‘C:\Users\dbown\Katalon Studio\Dan Test\androidapp\APIDemos.apk’ (Root cause: : An unknown server-side error occurred while processing the command. TC01 Verify Correct Alarm Message will complete Actual Behavior.
Choose the emulator or device you’re going to test on from the Device Name dropdown.You can edit the settings by going to Project->Settings and then expanding Desired Capabilities->Mobile->Android.You can set the Desired Capabilities settings to tell Katalon Studio (and the underlying Appium) how to launch an app. It looks like the app you’re testing might be using 2 different packages, and Appium doesn’t know which one to start. Hi sounds like an issue with the Desired Capability settings for appWaitActivity or appWaitPackage: