appium啟動失敗

㈠ appuim啟動報錯

啟動appium時，突然報錯，這時候關鍵看這句話：main.js: error: Unrecognized arguments: file\base.apk.

這里表示有個空找不著。

原因是上次打開時，不小心將設置中的package選中，導致每次啟動時，都會去檢查package。但是沒有使用package，就報錯了。因此把package前面的勾去掉，再次運行，即可啟動。

拓展資料：

appium 是一個自動化測試開源工具，支持 iOS 平台和 Android 平台上的原生應用，web應用和混合應用。

其特點有：

1.「移動原生應用」是指那些用iOS或者 Android SDK 寫的應用（Application簡稱app）。

2.「移動web應用」是指使用移動瀏覽器訪問的應用（appium支持iOS上的Safari和Android上的 Chrome）。

3.「混合應用」是指原生代碼封裝網頁視圖——原生代碼和 web 內容交互。比如，像 Phonegap，可以幫助開發者使用網頁技術開發應用，然後用原生代碼封裝，這些就是混合應用。

重要的是，appium是一個跨平台的工具：它允許測試人員在不同的平台（iOS，Android）使用同一套API來寫自動化測試腳本，這樣大大增加了iOS和Android測試套件間代碼的復用性。

appium是跨平台的，可以用在OSX，Windows以及Linux桌面系統上運行。

appium選擇了Client/Server的設計模式。只要client能夠發送http請求給server，那麼的話client用什麼語言來實現都是可以的，這就是appium及Selenium(WebDriver)如何做到支持多語言的原因；

appium擴展了WebDriver的協議，沒有自己重新去實現一套。這樣的好處是以前的WebDriver API能夠直接被繼承過來，以前的Selenium（WebDriver）各種語言的binding都可以拿來就用，省去了為每種語言開發一個client的工作量。

㈡ Appium運行java腳本，報錯Activity used to start app doesn't exist or cannot be launched!Make sure

1、在你的程序中，初始化appium設置的appActivity這項，值不對，不是當前被測app啟動時調用的activity

可以通過命令行aapt mp badging D:xxx.apk，可以檢查到此apk的packageName和activityName

要求先進去androidSDK的build-tools目錄下

㈢ 求大神解答，為什麼啟動 appium 啟動不了啊 · TesterHome

appium主要需要配置兩個地方，一個是sdk路徑，一個是ip+埠號

㈣ Appium超時錯誤連接到驅動程序時問題，怎麼解決

問題

1. error: Failed to start an Appium session, err was: Error: Requested a new session but one was in progress

之前的會話沒有關閉，然後你又運行了測試實例，也沒有設置覆蓋.
解決:
1.重新停止appium服務，開啟Appium服務
2.在Genarel Setting那裡設置覆蓋Session，重啟Appium

測試結束在AfterClass加driver.quit()

2. error: Failed to start an Appium session, err was: Error: Command failed: C:Windowssystem32cmd.exe /s /c "D:android-sdk-windowsplatform-toolsadb.exe -s adb server version (32) doesn't match this client (36); killing…

wait-for-device"
error: could not installsmartsocketlistener: cannot bind to 127.0.0.1:5037:

沒有鏈接上手機或者模擬器，請確認已經連接成功，重新鏈接

3. error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.

手機系統低於4.2，appium不支持4.2.2以下的系統，請換一個手機或者模擬器來測試。

4. Error: Permission to start activity denied.

**activity在清單文件裡面沒添加Android:exported="true"的話，你不能直接打開對應的activity，需要從啟動頁activity打開。
exported屬性就是設置是否允許activity被其它程序調用**

5. error: Failed to start an Appium session, err was: Error: Activity used to start app doesn't exist or cannot ve launched! Make usre it exists and is launchable activity

要打開的activity不存在，activity路徑錯誤，改為完整正確的activity路徑

6. error: Failed to start an Appium session, err was: Error: 'java - version' failed. Error: Command failed: C:Windowssystem32cmd.exe /s /c "java -version"

Java版本錯誤，請安裝最新的版本。

7.> info: [debug] Error: Command failed: C:Windowssystem32cmd.exe /s /c "D:android-sdk-windowsplatform-toolsadb.exe -s 8806a0b0 shell "echo 'ready'"error: unknown host service

鏈接手機失敗，重新鏈接手機即可，我就是重新拔插了一下usb

Error: Command failed: C:Windowssystem32cmd.exe /s /c "D:android-sdk-windowsplatform-toolsadb.exe -s 8806a0b0 shell "echo 'ping'""

error: unknown host service

adb被突然佔用導致，例如你在運行用例的時候運行了模擬器。

8. UIAutomatorViewer提示: Unable to connect to adb. Check if adb is installed correctly

解決，sdk升級到了25產生的問題。

解決方法:

• 將adb.exe復制一份到uiautomatorviewer.bat目錄下

• 修改uiautomatorviewer.bat文件最後一行（改binddir=%prog_dir%為自己的platform-tools本地路徑）
  

9 error: Failed to start an Appium session, err was:INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install io.appium.settings without first uninstalling

When you are at final step to execute test automation script for mobile app testing on a mobile emulator or a virtual device or a real device, you might observe that script execution fails with different kinds of errors, In context to current article you will look at the error and solutions for: INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install io.appium.settings without first uninstalling.

Error in Appium Server:

1

2

3

4

5

6

7

8

Error: Command failed: C:Windowssystem32cmd.exe /s /c

"C:Users{User}-toolsadb.exe -s

emulator-5554 install

"C:Program Files (x86)Appium ode_molesappiumuildsettings_apksettings_apk-debug.apk""

> Failed to install C:Program Files (x86)Appium ode_molesappiumuildsettings_apk

settings_apk-debug.apk: Failure [INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install

io.appium.settings without first uninstalling.]

Error in Android studio run console:

1

2

3

4

5

6

7

8

9

org.openqa.selenium.SessionNotCreatedException: A new session could not be created.

(Original error: Command failed: C:Windowssystem32cmd.exe /s /c

"C:Users{User}-toolsadb.exe -s emulator-5554 install

"C:Program Files (x86)Appium ode_molesappiumuildsettings_apksettings_apk-debug.apk""

Failed to install C:Program Files (x86)Appium ode_molesappiumuildsettings_apk

settings_apk-debug.apk: Failure [INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install

io.appium.settings without first uninstalling.]

) (WARNING: The server did not provide any stacktrace information)

Command ration or timeout: 0 milliseconds

For the first time when you execute the script itmight pass, but it will fail with above error when you try to execute the same or any other script multiple times. Or when your test script execution fails on the first attempt for some other reason, and when you fix it and execute it again, you might encounter this new issue.

原因：

The reason for this error is that Appium installs 2 mobile applications before executing the script.

1. io.appium.settings

2. io.appium.unlock

Theseare the supportive mobile applications appium utilizes to execute the test automation script in Mobile Emulator or virtual device or a real mobile device.

Ideally Appium should remove these files every time at the end of the script execution or termination, if it is intends to install themevery time a script is executed, or it should conditionally install these apps / apksto the mobile emulator or mobile device.

In your mobile emulator / Virtual Device / Real device, the 2 mobile applications appear as below:

There are multiple ways to troubleshootthis error and go ahead for asuccessful test script execution.

解決辦法

Solution 1: ADB's uninstall command to remove the files.

You can open command prompt, assuming that you already had set the environment variables for ANDROID_HOME and Path variables for sdk tools and platform tools.

And execute commands as shown below:

Solution 2: Uninstall manually

You can open the mobile emulator / virtual device / real device and go to apps and uninstall them.

Solution 3: Write code as part of your test automation script.

As part of your selenium test automation script, you could write instructions to execute the commands provided in solution 1 above, so that this issue would not arise.

Hope this article has been helpful and you are able to proceed further with script execution.

Request to kindly share any of your queries in form of comments, we would try our best to provide any solution for you.

10.出錯信息里含有"ps 'uiautomator'，具體信息未 A new session could not be created. (Original error: Command failed: C:Windowssystem32cmd.exe /s /c "C:Userssxie-toolsadb.exe -s emulator-5554 shell "ps 'uiautomator'""

android-appium: A new session could not be created

junitexceptionandroidappium自動化

detail log:
org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Command failed: C:Windowssystem32cmd.exe /s /c "C:Userssxie-toolsadb.exe -s emulator-5554 shell "ps 'uiautomator'""
) (WARNING: The server did not provide any stacktrace information)
Command ration or timeout: 0 milliseconds
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
System info: host: 'WL00070299', ip: '10.110.12.39', os.name: 'Windows 8.1', os.arch: 'x86', os.version: '6.3', java.version: '1.8.0_40'
Driver info: driver.version: AndroidDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect..newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:215)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:167)
at io.appium.java_client.remote.AppiumProtocolHandShake.createSession(AppiumProtocolHandShake.java:161)
at io.appium.java_client.remote.AppiumProtocolHandShake.createSession(AppiumProtocolHandShake.java:76)
at io.appium.java_client.remote.AppiumCommandExecutor.doExecute(AppiumCommandExecutor.java:111)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:162)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:637)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:250)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:236)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:137)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:88)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:112)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:73)
at com.sky.demo.ContactTest.setUp(ContactTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schele(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

==========================================
直接在cmd中執行"C:Windowssystem32cmd.exe /s /c "C:Userssxie-toolsadb.exe -s emulator-5554 shell "ps 'uiautomator'""
bad pid 'uiautomator'"， 報錯： bad pid 'uiautomator'

代碼內容為


public class ContactTest {
private AndroidDriver driver;
@Before
public void setUp() throws Exception {
//設置apk的路徑
File classpathRoot = new File(System.getProperty("user.dir"));
File appDir = new File(classpathRoot, "apps");
File app = new File(appDir, "ContactManager.apk");

• //設置自動化相關參數


• DesiredCapabilities capabilities = new DesiredCapabilities();


• capabilities.setCapability(CapabilityType.BROWSER_NAME, "");


• capabilities.setCapability("automationName","Appium");


• capabilities.setCapability("platformName", "Android");


• capabilities.setCapability("deviceName", "Pixel_XL_API_25");// Galaxy_Nexus_API_25


• capabilities.setCapability("noReset", true);


• capabilities.setCapability("avdReadyTimeout", 300000);


• capabilities.setCapability("sessionOverride", true);


• //設置安卓系統版本


• capabilities.setCapability("platformVersion", "7.1.1");


• //設置apk路徑


• capabilities.setCapability("app", app.getAbsolutePath());


• //設置app的主包名和主類名


• capabilities.setCapability("appPackage", "com.example.android.contactmanager");


• capabilities.setCapability("appActivity", ".ContactManager");


• //初始化


• driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);


• driver.manage().timeouts().implicitlyWait(10,TimeUnit.SECONDS);


• }


• @Test


• public void addContact(){


• WebElement el = driver.findElement(By.name("Add Contact"));


• el.click();


• List<WebElement> textFieldsList = driver.findElementsByClassName("android.widget.EditText");


• textFieldsList.get(0).sendKeys("feimaoyuzhubaobao");


• textFieldsList.get(2).sendKeys("forever together");


• driver.swipe(100, 500, 100, 100, 2);


• driver.findElementByName("Save").click();


• }


• @After


• public void tearDown() throws Exception {


• driver.quit();


• }



}

解決辦法：

resolved by this way:
adb.js(C:Program Files (x86)Appium ode_molesappium ode_molesappium-adblibadb.js) 中1035 行this.shell("ps '" + name + "'", function (err, stdout) {
對應執行的指令是ps 'uiautomator', Android7不支持這個指令格式，所以執行結果是bad pid 'uiautomator'
目前Appium未對此進行處理,所以需要修改此指令的執行方式
即將
this.shell("ps '" + name + "'", function (err, stdout) {
if (err) return cb(err);
替換成
this.shell_grep("ps", name, function (err, stdout) {

if (err) {

logger.debug("No matching processes found");
return cb(null, []);

}

並增加上面用到的shell_grep函數：
ADB.prototype.shell_grep = function (cmd, grep, cb) {
if (cmd.indexOf('"') === -1) {
cmd = '"' + cmd + '"';
}
var execCmd = 'shell ' + cmd + '| grep ' + grep;
this.exec(execCmd, cb);

};

11.Android 7.0系統的手機無法執行appium腳本的問題

AppiumAppium 版本 1.4.16，Android 設備固件 7.x，執行腳本時，報錯使用語言：python報錯如下：
WebDriverException: Message: A new session could not be created. (Original error: Could not extract PIDs from ps output. PIDS: [], Procs: ["bad pid 'uiautomator'"])

這個是因為appium版本1.4.16使用的uiatumator1.0不支持的原因導致？如果不升級appium版本，是否有解決方案？

解決辦法

uiautomator1.0應該是不支持7.0，不升版本就換用uiautomator2.0吧，或者用下面的改腳本的方法使用。

解決Android 7.0系統的手機無法執行appium腳本的問題，改問題的具體解決方法如下：

• 找到appium的安裝目錄下的adb.js文件，windows版本的目錄如下：Appium ode_molesappium ode_molesappium-adblib
  2、打開adb.js，手動修改該文件下的內容，此方法我已經試驗成功。

adb.js 中1035 行this.shell("ps '" + name + "'", function (err, stdout) {
對應執行的指令是ps 'uiautomator', Android7不支持這個指令格式，所以執行結果是bad pid 'uiautomator'
目前Appium未對此進行處理,所以需要修改此指令的執行方式
即將
this.shell("ps '" + name + "'", function (err, stdout) {
if (err) return cb(err);
替換成
this.shell_grep("ps", name, function (err, stdout) {

if (err) {

logger.debug("No matching processes found");
return cb(null, []);

}

並增加上面用到的shell_grep函數：
ADB.prototype.shell_grep = function (cmd, grep, cb) {
if (cmd.indexOf('"') === -1) {
cmd = '"' + cmd + '"';
}
var execCmd = 'shell ' + cmd + '| grep ' + grep;
this.exec(execCmd, cb);

};

• 網上還有如下的修改解決辦法：以下我未試驗。
  ADB.prototype.getPIDsByName = function (name, cb) {
  logger.debug("Getting all processes with '" + name + "'");
  this.shell("ps '" + name + "'", function (err, stdout) {
  if (err) return cb(err);
  stdout = stdout.trim();
  var procs = [];
  var outlines = stdout.split(" ");
  outlines.shift(); //在該處添加此行代碼
  3、重啟appium

技巧

1.每次測試都重新安裝app

為capabilities色設置noReset為true
capabilities.setCapability("noReset", true);

2.中文亂碼

這都是編碼問題:

1.方法1:

Android Studio修改文件編碼的方法，最底部的UTf-8,點擊選GBK就可以了，reload文件。（ps:先把文件內容全選復制一下再轉換編碼，再粘貼，不然文件內容就變亂碼了）

2.方法2:

用的是原來的UTF-8編碼，然後在測試mole的build.gradle裡面添加三行代碼

tasks.withType(JavaCompile){

options.encoding = 'UTF-8'

}

3.清除編輯框EditText內容

這個問題好像是看手機系統的，我之前的手機就會出現sendKeys的時候沒有全選去掉本來的內容，現在都會自動全選覆蓋了，這個也不算問題了。

/**

* 逐字刪除編輯框中的文字

* @param element 文本框架控制項

*/

public void clearText(AndroidElement element){

String className = element.getClass().getSimpleName();

if (className.equals("EditText")){

String text = element.getText();

//跳到最後

driver.pressKeyCode(KEYCODE_MOVE_END);

for (int i = 0; i < text.length(); i ++){

//循環後退刪除

driver.pressKeyCode(BACKSPACE);

}

}else {

print("不是文本輸入框架，無法刪除文字");

}

}

1

4.點擊輸入法鍵盤的回車搜索

方法1:切換輸入法

利用adb命令先切換為自己的輸入法，按了搜索再切換為appium的輸入法

查看當前手機的輸入法

cmd執行下面的的代碼

adb shell ime list -s

可以看到類似下面的結果，

C:UsersLITP>adb shell ime list -s

com..input_mi/.ImeService

com.sohu.inputmethod.sogou.xiaomi/.SogouIME

io.appium.android.ime/.UnicodeIME

C:UsersLITP>

執行adb命令

先寫好一個執行cmd的方法

/**

* 執行adb命令

* @param s 要執行的命令

*/

private void excuteAdbShell(String s) {

Runtime runtime=Runtime.getRuntime();

try{

runtime.exec(s);

}catch(Exception e){

print("執行命令:"+s+"出錯");

}

}

在需要搜索的時候執行下面的代碼，切換的輸入法用自己查看列表的輸入法內容，我這里是搜狗輸入法

//使用adb shell 切換輸入法-更改為搜狗拼音，這個看你本來用的什麼輸入法

excuteAdbShell("adb shell ime set com.sohu.inputmethod.sogou.xiaomi/.SogouIME");

//再次點擊輸入框，調取鍵盤，軟鍵盤被成功調出

clickView(page.getSearch());

//點擊右下角的搜索，即ENTER鍵

pressKeyCode(AndroidKeyCode.ENTER);

//再次切回 輸入法鍵盤為Appium unicodeKeyboard

excuteAdbShell("adb shell ime set io.appium.android.ime/.UnicodeIME");

㈤ 在cmd啟動appium出現如下問題，我的版本是1.4.16.1最高了，該怎麼解決

當前版本不支持某些模塊，不是最新的版本都向下兼容。考慮換個低版本的appium，1.4.0

如果appium-doctor沒有檢測出問題，可以先執行一段程序，看看具體初始化driver和識別是否報錯。再決定要不要更換版本