Appium appium 1.7.2 ChangeLog
Appium 1.7.2 is a feature and bug fix release. It fixes many issues found in earlier releases.
General
Fix memory leak in server logging
Add support for MacOS 10.13
Clean up logging to make messages more clear and useful
Add printPageSourceOnFindFailure to automatically log the current page source when finding an element or elements fails
Add ability to take screenshots of an element
Begin to handle Selenium W3C specification
iOS
Simulators
Clean up handling in Xcode 9
Add support for shake gesture (requires AppleScript)
Add support for custom geo locations (requires AppleScript)
Add possibility to clear caches
Make sure execution does not fail when trying to shut down simulators that are already shut down
Fix handling of source when within a frame/iframe, so that the source of the frame is retrieved instead of that of the top-most frameset
Fix error when unable to parse real device date/time, to return unparsable date rather than Invalid Date
Fix getting crash logs
Fix getting device logs in iOS 10+
Fix cleaning up of temporary files
Correctly handle device names for iPhone 7, 8 and X in Xcode 9
Fix screenshots for larger real devices
Fix runtime Xcode selection through DEVELOPER_DIR environment variable
Add useJSONSource desired capability to force Appium to use WDA JSON source and parse locally, to speed up source retrieval on larger devices
Fix file pushing/pulling so it works for simulators and real devices
iOS - Instruments-specific
Android
Fix handling of install/upgrade of Appium helper apps (for settings manipulation and unlocking of devices)
Add support for Chromedriver 2.33 (which supports webviews on Android O)
Add showChromedriverLog desired capability to bring Chromedriver logs in-line in the Appium server logs
Fix error in stopping coverage when session failed to start
Add support for getting and setting animation state
Fix handling of size-limited text fields in API levels below 24
Add support for getting the current value of progress bars
Fix handling of initial orientation, and make sure no orientation is set if nothing is requested
Make sure all UiAutomator commands are properly handled
Ensure pageLoadStrategy capability is passed to Chromedriver
Add support to get currently running package name
Ensure non-working Chromedriver is correctly handled --不明所以
Add password to retrievable element attributes
Fix locale/language setting
Add clearDeviceLogsOnStart desired capability, to clear adb logcat logs when the session is started
Add --relaxed-security, and mobile: shell access to adb
Jackey
回复
请问一下 Encountered internal error running command: TypeError: Invalid Version: android-4.4.2 你这个报错修复了吗？遇到了同样的问题
baozi255
回复
我去 appium 的 github 上面提问，找到了解决办法：
我们知道在 $ANDROID_HOME/build-tools 目录中。
$ ls $ANDROID_HOME/build-tools
一般来说，例如，我们可以看到以下结果，但是您的日志看起来是您 android-4.4W 命名的目录。
23.0.1 23.0.3 25.0.0 25.0.1 25.0.2 26.0.0 26.0.2
所以只需要把 build-tools 文件夹里面的 android-4.4W 重命名为 20.0.0 就好了。
如果报错的不是 4.4W，那么就把安卓文件夹改为对应的版本号就行了。这个版本的 appium 只能识别 23.0.1 这种文件夹，不能识别 android-4.4W 这种文件夹
曾志康
回复
我是 mac，今天在网上看了一下安装 appium 时不能用 sudo 可能会在后面导致问题，所以我就在终端用 sudo appium 启动的 appium，完了就没有报这个错误，并且执行了例程
[MJSONWP] Encountered internal error running command: TypeError: Invalid Version: android-4.4
at new SemVer (C:\Users\Administrator\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\semver\semver.js:293:11)
at compare (C:\Users\Administrator\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\semver\semver.js:566:10)
at rcompare (C:\Users\Administrator\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\semver\semver.js:576:10)
at Array.sort (native)
同样的问题，期待解决方法。
water
回复
“ Failed at the appium-chromedriver@3.1.4 install script”
设置一个环境变量重定向 chromedriver 下载地址,方法如下:
windows:
set CHROMEDRIVER_CDNURL=http://npm.taobao.org/mirrors/chromedriver/
Linux 或 MAC:
export CHROMEDRIVER_CDNURL=http://npm.taobao.org/mirrors/chromedriver/
然后再执行安装命令,您会发现下载链接变成 taobao 的了
Appium 1.7.2 python，红米 note3 ，android 5.1.1 手机，启动就报无效的 android 版本：Encountered internal error running command: TypeError: Invalid Version: android-4.4.2
重装 appium 还是报这个错，郁闷死了
1.7.2 一直安装不上：
34157 verbose stack Error: appium-chromedriver@3.1.4 install: `node install-npm.js`
34157 verbose stack Exit status 1
34157 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
34157 verbose stack at emitTwo (events.js:125:13)
34157 verbose stack at EventEmitter.emit (events.js:213:7)
34157 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
34157 verbose stack at emitTwo (events.js:125:13)
34157 verbose stack at ChildProcess.emit (events.js:213:7)
34157 verbose stack at maybeClose (internal/child_process.js:897:16)
34157 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
34158 verbose pkgid appium-chromedriver@3.1.4
34159 verbose cwd /usr/local/lib/node_modules
34160 verbose Darwin 17.3.0
34161 verbose argv "/usr/local/Cellar/node/8.1.4/bin/node" "/usr/local/bin/npm" "install" "appium"
34162 verbose node v8.1.4
34163 verbose npm v5.6.0
34164 error code ELIFECYCLE
34165 error errno 1
34166 error appium-chromedriver@3.1.4 install: `node install-npm.js`
34166 error Exit status 1
34167 error Failed at the appium-chromedriver@3.1.4 install script.
34167 error This is probably not a problem with npm. There is likely additional logging output above.
34168 verbose exit [ 1, true ]
赞~~一起发现的,哈哈