首页 文章

Appium Error UI Automator

提问于
浏览
0

WINDOWS 7 Appium:1.4.16.1来自Android Virtual Device Manager的Emulator Android

APPIUM REST响应:

谢谢你让我知道 . 如果你想到可能是什么原因 .

来自ECLIPSE的代码:

'import org.openqa.selenium.By;
 import org.openqa.selenium.chrome.ChromeDriverService;
 import org.openqa.selenium.remote.DesiredCapabilities;
 import org.openqa.selenium.remote.RemoteWebDriver;
 import org.testng.annotations.AfterClass;
 import org.testng.annotations.BeforeClass;
 import org.testng.annotations.Test;
 import java.io.File;
 import java.io.IOException;
 import java.net.MalformedURLException;
 import java.net.URL;
 import io.appium.java_client.MobileElement;
 import io.appium.java_client.android.AndroidDriver;
 import io.appium.java_client.ios.IOSElement;
 import io.appium.java_client.remote.MobileBrowserType;
 import io.appium.java_client.remote.MobileCapabilityType;
 import io.appium.java_client.remote.MobilePlatform;
 import org.openqa.selenium.Platform;
 import org.openqa.selenium.WebDriver;
 import org.openqa.selenium.remote.BrowserType;
 import java.util.concurrent.TimeUnit;

 //WebDriver driver;
 public class AA_Android1

 @Test
 public void test1() throws MalformedURLException, InterruptedException{

 DesiredCapabilities capabilities = new DesiredCapabilities();
 File app = new File("C:/Users/dd/Downloads/com.google.android.gm.4.5.apk");
 capabilities.setCapability(MobileCapabilityType.DEVICE_NAME,"emulator-      5554");
 capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, "Android");
 capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, "BROWSER");
 capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION, "6.0");
 capabilities.setCapability("appPackage", "com.android.browser");
      capabilities.setCapability("appActivity","com.android.browser.BrowserActivity");          

 capabilities.setCapability("browserName", MobileBrowserType.BROWSER);

 WebDriver driver = new AndroidDriver<MobileElement>(new              URL("http://127.0.0.1:4723/wd/hub"), capabilities );//error?
 driver.manage().timeouts().implicitlyWait(15, TimeUnit.SECONDS);'

APPIUM日志:'>使用命令启动Appium服务器:C:\ Appium \ node.exe lib \ server \ main.js --address 127.0.0.1 --port 4723 - 浏览器名称Chrome --session-override --platform -name Android --platform-version 23 --automation-name Appium --device-name“emulator-5554”--log-no-color

info:欢迎使用Appium v1.4.16(REV ae6877eff263066b26328d457bd285c0cc62430d)信息:Appium REST http接口监听器在127.0.0.1:4723上启动信息:[debug]非默认服务器args:{“address”:“127.0.0.1”,“ sessionOverride “:真实的,” logNoColors “:真实的,” 设备名称 “:” 模拟器-5554" , “platformName”: “机器人”, “platformVersion”: “23”, “automationName”: “Appium”, “browserName”:” Chrome“}信息:控制台LogLevel:调试信息: - > POST / wd / hub / session {”capabilities“:{”desiredCapabilities“:{”appPackage“:”com.android.browser“,”appActivity“:”com .android.browser.BrowserActivity”, “platformVersion”: “6.0”, “browserName”: “浏览器”, “platformName”: “机器人”, “设备名”: “模拟器-5554”}, “requiredCapabilities”:{}} “desiredCapabilities”:{ “appPackage”: “com.android.browser”, “appActivity”: “com.android.browser.BrowserActivity”, “platformVersion”: “6.0”, “browserName”: “浏览器”,“platformName “:”Android“,”deviceName“:”emulator-5554“},”requiredCapabilities“:{}} info:客户端用户代理字符串:Apache-HttpClient / 4.5.2(Java / 1.8.0_121)信息:设置模式:直接进入Chromedriver信息:[debug]看起来我们想在android上输入chrome:[debug]创建新的appium session 6f152533-ef46-4327-9543-c62fb07906ad info:[debug] Checking adb是否存在信息:[debug]使用来自C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe信息的adb:[debug]使用快速重置?真实信息:[debug]为会话信息准备设备:[debug]不检查app是否存在因为我们假设它已经在设备信息上:检索设备信息:[debug]试图找到连接的android设备信息:[debug ]连接设备...信息:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe设备信息:[debug] 1个设备连接信息:找到设备模拟器-5554信息:[debug]将设备ID设置为emulator-5554 info:[debug]等待设备准备就绪并响应shell命令(timeout = 5)info:[debug] execution cmd:C: \ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554等待设备信息:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell“echo'ready'”info:[debug]启动logcat捕获信息:[debug]将解锁帮助应用程序推送到设备... info:[debug] execution cmd:C:\ Users \ ddaunay \ AppData \ Local \ Andro id \ sdk \ platform-tools \ adb.exe -s emulator-5554安装“C:\ Appium \ node_modules \ appium \ build \ unlock_apk \ unlock_apk-debug.apk”info:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell“dumpsys window”info:[debug]屏幕已解锁,继续 . info:[debug]转发系统:4724到设备:4724信息:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 forward tcp :4724 tcp:4724 info:[debug]将appium bootstrap推送到设备... info:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 push“C:\ Appium \ node_modules \ appium \ build \ android_bootstrap \ AppiumBootstrap.jar”/ data / local / tmp / info:启动应用信息:[debug]试图杀死所有'uiautomator'进程信息:[debug ]使用'uiautomator'获取所有进程信息:[debug]执行cmd:C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell“ps'uiautomator'”信息:[调试]清理appium会话错误:无法启动Appium会话,错误是:错误:命令失败:C:\ Windows \ system32 \ cmd.exe / s / c“C:\ Users \ ddaunay \ AppData \本地\ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell“ps'uiautomator'”“info:[debug] Err或:命令失败:C:\ Windows \ system32 \ cmd.exe / s / c“C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell”ps ChildProcess.exithandler上的'uiautomator'“”(child_process.js:751:12)
在ChildProcess.emit(events.js:110:17)
在maybeClose(child_process.js:1016:16)
在Process.ChildProcess._handle.onexit(child_process.js:1088:5)
info:[debug]响应客户端错误:{“status”:33,“value”:{“message”:“无法创建新会话 . (原始错误:命令失败:C:\ Windows \ system32 \ cmd.exe / s / c \“C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell \”ps'uiautomator'\“\”\ n) “,”kill“:false,”code“:1,”signal“:null,”cmd“:”C:\ Windows \ system32 \ cmd.exe / s / c \“C:\ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator -5554c \“\”“,”origValue“:”命令失败:C:\ Windows \ system32 \ cmd.exe / s / c \“C: \ Users \ ddaunay \ AppData \ Local \ Android \ sdk \ platform-tools \ adb.exe -s emulator-5554 shell \“ps'uiautomator'\”\“\ n”},“sessionId”:null} info:< - POST / wd / hub / session 500 10097.767 ms - 679 info:[debug] Logcat以代码0终止,信号为空'

1 回答

  • 0

    在使用Appium 1.4.16版本时,我们遇到了类似的问题,我们在不同的论坛和appium相关支持列中搜索了很多 . 我们知道这是一个问题,他们为用户提供了一个替代方案,让他们继续工作,直到他们在下一个版本中解决这个问题 .

    基本上我们需要修改appium文件夹中的文件adb.js:C:\ Program Files(x86)\ Appium \ node_modules \ appium \ node_modules \ appium-adb \ lib \

    清楚地起草了这些细节@ http://www.testingtools.co/appium/error-command-failed-adb-exe-s-emulator-5554-shell-ps-uiautomator

    希望它有所帮助,你将成为abl

相关问题