Appium 2.0 beta cannot start a session on some Windows OS machines
See original GitHub issueThe problem
I am trying to start a test against new Appium Beta-25 version, with real Android device, on top of Windows 10 OS machine. The problem is that appium is showing an error on the appium server side as follow:
[HTTP] {"capabilities":{"firstMatch":[{"appium:noReset":true,"appium:fullReset":false,"appium:appPackage":"com.shs.wanderguard","appium:appActivity":"com.shs.wanderguard.activity.SplashActivity","appium:udid":"HGAGTKE7","appium:automationName":"UiAutomator2","appium:uiautomator2ServerInstallTimeout":"120000","appium:app":"C:\\workspace\\builds\\wg\\wg.apk","appium:newCommandTimeout":"500","appium:allowTestPackages":true,"appium:autoGrantPermissions":true,"appium:wdaLocalPort":"4723","platformName":"Android"}]},"desiredCapabilities":{"noReset":true,"fullReset":false,"appPackage":"com.shs.wanderguard","appActivity":"com.shs.wanderguard.activity.SplashActivity","udid":"HGAGTKE7","automationName":"UiAutomator2","uiautomator2ServerInstallTimeout":"120000","app":"C:\\workspace\\builds\\wg\\wg.apk","newCommandTimeout":"500","allowTestPackages":true,"autoGrantPermissions":true,"wdaLocalPort":"4723","platformName":"Android"}}
[debug] [HTTP] No route found for /wd/hub/session
[HTTP] <-- POST /wd/hub/session 404 1 ms - 211
[HTTP]
appiu[Appium] Received SIGINT - shutting down
[debug] [Appium] There are no active sessions for cleanup
[HTTP] Waiting until the server is closed
[HTTP] Received server close event
The problem is not happening on top of Mac OS machine.
I am starting the appium server with the following CLI command:
appium --base-path /wd/hub
Environment
- Appium version (or git revision) that exhibits the issue: 2.0.0-beta.25
- Last Appium version that did not exhibit the issue (if applicable): 1.22.1
- Desktop OS/version used to run Appium: Windows OS 10
- Node.js version (unless using Appium.app|exe): v16.13.2
- Npm or Yarn package manager: npm
- Mobile platform/version under test: Android OS 8
- Real device or emulator/simulator: Real device
- Appium CLI or Appium.app|exe: Appium CLI
Details
- Listing available drivers √ Listing available drivers
- windows@2.0.1 [installed (NPM)]
- uiautomator2@2.0.3 [installed (NPM)]
Link to Appium logs
https://github.com/bwomsm1/AppiumLogs/blob/master/appium_win.log
Code To Reproduce Issue [ Good To Have ]
Just try to launch any empty test on Windows OS env
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Troubleshooting - Appium
General · Make sure you've followed the getting started steps in the README · Make sure your system is set up appropriately (i.e.,...
Read more >Appium 2.0 - State of the Union by Jonathan Lipps ... - YouTube
The last few years have been huge for the world of automation, and they only serve to underscore the importance of Appium's mission:...
Read more >First Look at Appium 2.0 and New Drivers - HeadSpin
A first look on what Appium 2.0 is, what's the vision, and what are some of the technical possibilities and changes that you...
Read more >appium-uiautomator2-driver - npm
Start using appium-uiautomator2-driver in your project by running `npm ... other projects in the npm registry using appium-uiautomator2-driver.
Read more >Appium Server and Inspector in Desktop GUIs for Mac, Windows ...
Connect to local Appium server; Appium can't detect environment variables on Mac; Warnings about being on a read-only file system. Developer Instructions ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it looks like this is the issue: https://github.com/moby/moby/issues/24029. so it’s git-bash’s fault. the workaround/solution is here. i.e.
you may want to export that env var so it’s always on for your terminal sessions.
closing this issue since we’ve confirmed this is a git bash issue, not an Appium one.
GitBash