Articles
技術文章
Appium 與行動測試自動化的實務筆記:卡住測試的錯誤、真正的原因,以及讓測試穩定的修法。文章內文為英文。
Appium "Could not find a driver for automationName": how Appium matches drivers and why it misses
What Appium 2 and 3 actually check when a session asks for UiAutomator2 or XCUITest, how to read the lower-level error at the end of the message, and the usual causes: no driver installed, a different APPIUM_HOME, a project-local Appium, and a broken install.
Appium UiAutomator2 "instrumentation process is not running (probably crashed)" and "socket hang up": causes and fixes
Both errors mean the UiAutomator2 server on the Android device is gone. How the driver starts and watches that server, what each message means, and the usual reasons it stops: overlapping sessions, the device killing it, and a dropped adb connection.
Appium StaleElementReferenceException on Android and iOS: the mobile causes and fixes
On mobile, a stale element is decided by an element cache on the device, not by a browser DOM. What the UiAutomator2 and WebDriverAgent error messages mean, which app behaviors cause them, and how to fix each one.
Appium WebDriverAgent slow startup: where the time goes and how to cut it in CI
Why iOS Appium sessions spend so long waiting for WebDriverAgent to start, how to read the startup from the server log, and the four ways to stop running xcodebuild in every session — with the trade-offs of each.
Appium “xcodebuild failed with code 65”: what it means and how to fix it
Code 65 means WebDriverAgent failed to build or sign — it is not the real error. How to surface the actual xcodebuild failure, fix signing, keychain and device setup, and stop it recurring in CI.