After updating to appium 1.20.0 UnknownError happens on every test run
See original GitHub issueThe problem
Since I updated to appium 1.20.0, all my android tests trigger this error
UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded
Environment
- Appium version: 1.20.0
- Last Appium version that did not exhibit the issue: 1.19.1
- Desktop OS/version used to run Appium: macOs catalina 10.15.7
- Node.js version: v14.4.0
- Npm: 6.14.4
- Mobile platform/version under test: Android API 30 x86
- emulator/simulator: Pixel 3
- Appium CLI
- Capabilities:
automationName: UiAutomator2
platformName: Android
deviceName: Pixel_3_API_30
app: app_path
appPackage: app_package
appActivity: app_main_activity_name
udid: "emulator-5554"
autoGrantPermissions: true
newCommandTimeout: 60
Link to Appium and ADB logs:
Appium logs: https://gist.github.com/aguspeq/7517cd1b2a16033f7eaf135b43d0d649 ADB logs: https://gist.github.com/aguspeq/070454971b0d1bb80ff0878d1cdade7c
Code To Reproduce Issue
The code is written in ruby, it happens when I call this method and it cannot find the element:
driver.find_elements(accessibility_id: 'log_ind')
Notes
- I have not modified my code before this issue happened
- I just ran my whole suite after updating to 1.20.0
- All my iOS tests works fine
- I have tried with Android API 8.1 x 86 on a Nexus 6p emulator and the issue is the same
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Troubleshooting - Appium
If Instruments is crashing when running against a physical device ("exited with code 253"), ensure Xcode has downloaded device symbols. Go to Window...
Read more >Appium: UnknownError: An unknown server-side error ...
This exception is usually thrown, when io.appium.uiautomator2.server application is killed on Android side. It's possible that system kills ...
Read more >NoSuchElementException occurs on android when executed ...
NoSuchElementException occurs on android when executed using appium version 1.20.0 or more. I am executing the script on React-native ...
Read more >How to Install Appium on Mac OS with Required Tools
We need this tool for running our tests on real devices. In order to install it, open a terminal window and run the...
Read more >Capabilities for running mobile app tests on BrowserStack
Default & BrowserStack specific capabilities for App Automate, to run Appium tests with support for Local Testing, Debugging and 3000+ Mobile & Desktop ......
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
Could you append around logs for the logcat and run with
--log-timestamp
for appium server to check the timeline? It is also appreciated to attach the full appium server log.For logcat: Probably like
xxxx /io.appium.uiautomator2.server I/appium: channel read: POST /wd/hub/session/yyyyy/element
log exists in the logcat after getting a request.Closed as not an issue