Cannot set implicit wait on Android.
See original GitHub issueThe problem
Still seeing issues when setting implicit wait while using W3C (forcing MSJONWP through MobileCapabilityType.FORCE_MJSONWP works fine). This issue is related to this closed issue. As stated in the original issue everything works fine with Appium 1.8.1.
Environment
- Appium version (or git revision) that exhibits the issue: 1.8.2-beta
- Last Appium version that did not exhibit the issue (if applicable): 1.8.1
- Desktop OS/version used to run Appium: Windows 10
- Node.js version (unless using Appium.app|exe): v8.0.0
- Mobile platform/version under test: Android 8.0
- Real device or emulator/simulator: real device, hybrid webview app
- Appium CLI or Appium.app|exe: Appium CLI
Details
Error response
[HTTP] --> POST /wd/hub/session/e66113e6-0bde-4a3c-8b53-066a15510bb8/timeouts
[HTTP] {"implicit":1000}
[W3C] Driver proxy active, passing request on via HTTP proxy
[debug] [JSONWP Proxy] Matched '/wd/hub/session/e66113e6-0bde-4a3c-8b53-066a15510bb8/timeouts' to command name 'timeouts'
[debug] [JSONWP Proxy] Proxying [POST /wd/hub/session/e66113e6-0bde-4a3c-8b53-066a15510bb8/timeouts] to [POST http://127.0.0.1:8000/wd/hub/session/8d237d70c8d8c81541220680d1aac4c4/timeouts] with body: {"implicit":1000}
[debug] [JSONWP Proxy] Got response with status 200: {"sessionId":"8d237d70c8d8c81541220680d1aac4c4","status":13,"value":{"message":"unknown error: 'ms' must be a double\n (Session info: chrome=67.0.3396.87)\n (Driver info: chromedriver=2.41.578737 (49da6702b16031c40d63e5618de03a32ff6c197e),platform=Windows NT 10.0.17134 x86_64)"}}
[W3C] Encountered internal error running command: {"w3cStatus":400,"jsonwp":{"sessionId":"8d237d70c8d8c81541220680d1aac4c4","status":13,"value":{"message":"unknown error: 'ms' must be a double\n (Session info: chrome=67.0.3396.87)\n (Driver info: chromedriver=2.41.578737 (49da6702b16031c40d63e5618de03a32ff6c197e),platform=Windows NT 10.0.17134 x86_64)"}}} ProxyRequestError: Could not proxy command to remote server. Original error: The request to /wd/hub/session/e66113e6-0bde-4a3c-8b53-066a15510bb8/timeouts has failed
Link to Appium logs
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
APPIUM Android: Implicit wait and explicit wait are not working
Defined the implicit wait and pageLoadTimeout after Android driver is initialized with required desired capabilities and URL. Defined implicit ...
Read more >Implicit & Explicit wait is not reliable to find the element - Support
Hi, I am running the appium test for hybrid app on iOS. I am using the wait condition until the element is clickable.But...
Read more >How to use implicit and explicit waits in Selenium. - ITNEXT
The implicit (indirect, hidden) wait is set once in the code outside the search operation and is valid until the change. The default...
Read more >Implicit and Explicit Wait in Appium - YouTube
Your browser can't play this video. Learn more. Switch camera.
Read more >Implicit wait | Mobile Test Automation with Appium
Implicit wait is a way to tell the Appium driver to poll the DOM (Document Object Model) for a certain amount of time...
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
The change has been published to appium@beta
@mykola-mokhnach Since this is Android using a webview i updated the appium-base-driver inside appium-chromedriver. Now everything works correctly with W3C. Thank you for the fast response and help!