appium: Error when trying to connect to an Appium server in a Selenium Grid

The problem

I got Error code while I was trying to run tests through Selenium grid, the driver was created and app opened but shortly after I got a status code 500 error. I’m using Ruby client.

Environment

  • Appium version (or git revision) that exhibits the issue: 1.6.4
  • Desktop OS/version used to run Appium: Windows 10 1607
  • Node.js version (unless using Appium.app|exe): 6.10.0
  • Mobile platform/version under test: Android 6.0.1
  • Real device or emulator/simulator: Samsung Galaxy A5 2017
  • Appium CLI or Appium.app|exe: CLI

Details

I tried with Node JS client, and there seems to be no problem. However the only thing I did is creating then quiting a driver.

Link to Appium logs

https://gist.github.com/GhenTerr

Code To Reproduce Issue [ Good To Have ]

All the code does it open the message app and click the new message button, that’s it

require 'appium_lib'

desired_caps = {
  caps:       {
    platformName: 'Android',
    platformVersion: '6.0.1',
    deviceName: 'Galaxy A5 (2017)',
    appPackage: 'com.samsung.android.messaging',
    appActivity: 'com.android.mms.ui.ConversationComposer'
  },
  appium_lib: {
    server_url: 'http://192.168.43.78:4444/wd/hub'
  }
}

driver = Appium::Driver.new(desired_caps)
driver.start_driver()
driver.find_element(:xpath, '//*[@resource-id="com.samsung.android.messaging:id/floating_action_button"]').click();

driver.driver_quit

Also the config json

`{
    "capabilities": [{
        "browserName": "Galaxy A5 (2017)",
        "version": "6.0.1",
        "platform": "Android",
        "maxInstances": 1
    }],
    "configuration": {
        "cleanUpCycle": 2000,
        "timeout": 30000,
        "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
        "url": "http://127.0.0.1:5000/wd/hub",
        "host": "127.0.0.1",
        "port": 5000,
        "maxSession": 1,
        "register": true,
        "registerCycle": 5000,
        "hubPort": 4444,
        "hubHost": "127.0.0.1"
    }
}`

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 18 (11 by maintainers)

Most upvoted comments

It seems to be fixed! I tested it with Selenium server 3.2.0 and 3.4.0. Thanks!