io.appium.java_client.ios.IOSDriver

perfectomobile.com | 4 months ago
  1. 0

    "xct launchapp failed" error on browser-goto command - iOS 10

    GitHub | 1 month ago | igorstd7
    org.openqa.selenium.WebDriverException: Failed to execute command browser goto: browser-url command failed. Reason: handset server: xct launchapp failed! Command duration or timeout: 78.38 seconds Build info: version: '2.53.1', revision: 'a36b8b1cd5757287168e54b817830adce9b0158d', time: '2016-06-30 19:26:09' System info: host: 'ws-igord-10', ip: '172.30.200.113', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_60' Driver info: com.qmetry.qaf.automation.ui.webdriver.QAFExtendedWebDriver Capabilities [{reportPdfUrl=http://reporting-int.aws-stg.perfectomobile.com/export/api/v1/test-executions/pdf?externalId[0]=test_automation@gmail.com_RemoteWebDriver_16-12-12_15_09_02_417, available=false, language=English, deviceName=9A90117A5FF7AEB655944A1D7FA8C70F3C2C81BD, deviceId=9A90117A5FF7AEB655944A1D7FA8C70F3C2C81BD, resolution=1242x2208, platform=ANY, wifiMacAddress=0c:d7:46:6f:bc:9a, manufacturer=Apple, mode=CONNECTED, password=, cradleId=WF-CD18-3-3/VIRTUAL/03, osVersion=10.1.1, automationName=Appium, host=system-tests.perfectomobile.com, singleTestReportUrl=https://system-tests.perfectomobile.com/nexperience/singletest/report/?reportRepositoryKey=PRIVATE:RemoteWebDriver/161212/RemoteWebDriver_16-12-12_15_09_02_417.xml&ownerId=test_automation@gmail.com&sharingCode=8cbd17ff-5fc4-42a6-95a7-5ec1fd171f08, inUse=true, takesScreenshot=true, browserName=MobileOS, javascriptEnabled=true, model=iPhone-6S Plus, firmware=10.1.1, rotatable=true, testGridReportUrl=https://system-tests.reporting-stg.perfectomobile.com?externalId[0]=test_automation@gmail.com_RemoteWebDriver_16-12-12_15_09_02_417, os=iOS, entityType=remote_web_driver, allocatedTo=test_automation@gmail.com, serverConnector=, executionId=test_automation@gmail.com_RemoteWebDriver_16-12-12_15_09_02_417, webdriver.remote.sessionid=041abaff-b3ea-4d35-97dd-eaeac2ca7437, locationContextEnabled=true, scriptName=RemoteWebDriver, location=NA-US-BOS, linkType=lab, reportKey=PRIVATE:RemoteWebDriver/161212/RemoteWebDriver_16-12-12_15_09_02_417.xml, windTunnelReportUrl=https://system-tests.perfectomobile.com/nexperience/singletest/report/?reportRepositoryKey=PRIVATE:RemoteWebDriver/161212/RemoteWebDriver_16-12-12_15_09_02_417.xml&ownerId=test_automation@gmail.com&sharingCode=8cbd17ff-5fc4-42a6-95a7-5ec1fd171f08, user=, operabilityRatingScore=100, cssSelectorsEnabled=true, status=Connected}] Session ID: 041abaff-b3ea-4d35-97dd-eaeac2ca7437 at .Given I open browser to webpage "http://www.nxc.co.il/E2ETesting/General/form.html"(src/main/resources/scenarios/TagsTests1.feature:6)
  2. 0
    If the decompile process didn't work properly, try the Android APK Decompiler.
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0
    Switch to Android Build Tools 23.0.3
  5. 0
    SMS Emulator caused this error. abortBroadcast only works with broadcasts sent through Context.sendOrderedBroadcast.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.RuntimeException

      Failed to execute command handset setup: No credentials found in association with the netem server whose ip is 1.90.15.4

      at com.perfectomobile.selenium.MobileEntity.processCommonResponse()
    2. com.perfectomobile.selenium
      PerfectoMobileDriver.<init>
      1. com.perfectomobile.selenium.MobileEntity.processCommonResponse(MobileEntity.java:98)
      2. com.perfectomobile.selenium.MobileDevice.processResponse(MobileDevice.java:503)
      3. com.perfectomobile.selenium.MobileEntity.executeCommand(MobileEntity.java:57)
      4. com.perfectomobile.selenium.MobileEntity.executeCommand(MobileEntity.java:50)
      5. com.perfectomobile.selenium.MobileDevice.setup(MobileDevice.java:658)
      6. com.perfectomobile.selenium.server.SetupCapabilities.execute(SetupCapabilities.java:44)
      7. com.perfectomobile.selenium.server.PerfectoMobileDriver.setupDevice(PerfectoMobileDriver.java:192)
      8. com.perfectomobile.selenium.server.PerfectoMobileDriver.<init>(PerfectoMobileDriver.java:87)
      8 frames
    3. Java RT
      Constructor.newInstance
      1. sun.reflect.GeneratedConstructorAccessor1068.newInstance(Unknown Source)
      2. sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
      3. java.lang.reflect.Constructor.newInstance(Constructor.java:526)
      3 frames
    4. selenium-server
      DefaultSession$BrowserCreator.call
      1. org.openqa.selenium.remote.server.DefaultDriverProvider.callConstructor(DefaultDriverProvider.java:103)
      2. org.openqa.selenium.remote.server.DefaultDriverProvider.newInstance(DefaultDriverProvider.java:97)
      3. org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:60)
      4. org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:222)
      5. org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:209)
      5 frames
    5. Java RT
      FutureTask.run
      1. java.util.concurrent.FutureTask.run(FutureTask.java:262)
      1 frame
    6. selenium-server
      DefaultSession$1.run
      1. org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
      1 frame
    7. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      3. java.lang.Thread.run(Thread.java:744)
      3 frames