Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    How to check the radio button is visible or not by appium?
    I ran into problem: Trying to proxy a session command without session id
    Tried different versions of Appium and emulators
    Creating new AndroidUiautomator2Driver (v1.19.0) session
    [Appium] Capabilities:
    [Appium] adbPort: 5037
    [Appium] automationName: UIAutomator2
    [Appium] browserName: Browser
    [Appium] deviceName: Pixel2
    [Appium] language: en
    [Appium] locale: US
    [Appium] platformName: Android
    [Appium] platformVersion: 7.1.1
    [Appium] skipServerInstallation: true
    [Appium] systemPort: 8201
    [Appium] newCommandTimeout: 0
    [Appium] connectHardwareKeyboard: true
    [BaseDriver] Creating session with MJSONWP desired capabilities: {"adbPort":"5037","automati...
    [BaseDriver] Capability 'systemPort' changed from string ('8201') to integer (8201). This may cause unexpected behavior
    [BaseDriver] Capability 'adbPort' changed from string ('5037') to integer (5037). This may cause unexpected behavior
    [BaseDriver] The following capabilities were provided, but are not recognized by appium: skipServerInstallation, connectHardwareKeyboard.
    [BaseDriver] Session created with session id: 8ced98cc-21e3-46af-b8d4-80f4269d1c57
    [UiAutomator2] We're going to run a Chrome-based session
    [UiAutomator2] Chrome-type package and activity are com.android.browser and com.android.browser.BrowserActivity
    [AndroidDriver] Java version is: 1.8.0_201
    [AndroidDriver] Retrieving device list
    [ADB] Trying to find a connected android device
    [ADB] Getting connected devices...
    [ADB] 1 device(s) connected
    [AndroidDriver] Looking for a device with Android '7.1.1'
    [ADB] Setting device id to emulator-5554
    [ADB] Getting device platform version
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.release'
    [ADB] Current device property 'ro.build.version.release': 7.1.1
    [AndroidDriver] Using device: emulator-5554
    [ADB] Setting device id to emulator-5554
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk'
    [ADB] Current device property 'ro.build.version.sdk': 25
    [ADB] Device API level: 25
    [AndroidDriver] No app sent in, not parsing package/activity
    [ADB] Getting device platform version
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.release'
    [ADB] Current device property 'ro.build.version.release': 7.1.1
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell wm size'
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell wm density'
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.product.model'
    [ADB] Current device property 'ro.product.model': Android SDK built for x86
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.product.manufacturer'
    [ADB] Current device property 'ro.product.manufacturer': Google
    [ADB] Device API level: 25
    [ADB] Running 'C:\Users\HP2\android-sdk-windows\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server'
    [ADB] Checking app cert for C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v1.18.0.apk
    [ADB] Starting 'C:\Users\HP2\android-sdk-windows\build-tools\29.0.1\apksigner.bat' with args '["verify","--print-certs","C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v1.18.0.apk"]'
    [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
    [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
    [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
    [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
    [ADB] WARNING: META-INF/INDEX.LIST not protected by signature. Unauthorized modifications to this JAR
    Roc Itxart Alba
    Hello All!
    did someone tried to open appium with iOS 13?
    I'm trying to run the inspector, simulator and app are launched
    but the view never loads
    Roc Itxart Alba
    did someone manage to run it?
    Salhi Aissam
    I've run into exactly the same problem using appium with iOS 13.
    App launches but inspector doesn't see anything in the view hierarchy of the app
    Roc Itxart Alba
    Also I've managed to run the test
    but doesn't find some of the elements
    [Chromedriver] Cannot retrieve version number from 'chromedriver.exe' Chromedriver binary. Make sure it returns a valid version string in response to '--version' command line argument. Cannot parse the version string
    Anybody meet with it?
    Hi I tried using Appium with desktop application and appium is not updating the main window after splash screen goes off. I want want inspect the elements after splash screen has gone.
    I am trying to automate a desktop application. It has html elements inside wpf container. I tried using inspect.exe and it is not able to inspect the element inside the html wpf panel. Could some let me know if its automate able using appium?
    Preeti Sharma
    This message was deleted
    Razvan Creanga
    I managed to run iOS tests after installing appium beta 'npm install -g appium@beta'
    some tests are failing though, I'm still investigating the cause
    Roc Itxart Alba
    @razvanu_twitter I did same
    But 90% of my test cases fail traying to click on a button
    so they never log in
    Razvan Creanga
    I have similar issues
    also switching to from native view to webview doesn't seem to be working
    selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: No targets found, unable to communicate with device
    this is the error I get
    seems like is switching to webview but I cannot inspect anything
    contexts = driver.contexts
        webview = driver.contexts[1]
        print('Current view ' + webview) # it prints WEBVIEW_66846.1
        driver.switch_to.context(webview) - here is failing
    this used to work for months, I'll try to debug it
    Roc Itxart Alba
    So far then.. iOS 13 is not working
    I don't even know what's the best thing to do: wait for a newer version of iOS version to be released (a new beta) or a new appium version. On my end it's okish, 30% of tests are failing and apart from the webview context switch all tests are fairly easy to fix.
    Wim Selles


    Appium doesn't officially support iOS 13 yet, meaning the current versions will not work 100%

    When iOS 13 will come out a new version will be released, but keep in mind it is open source, meaning it can take some time

    Níkolas Escobar

    Hey guys,

    [RemoteDebugger] Executing atom 'execute_script'
    [W3C (2d1b2b68)] Encountered internal error running command: Error: Unable to load Atom 'execute_script' from file 'C:\Program Files\Mobile Center Server\server\appium113\node_modules\appium-remote-debugger\build\atoms\execute_script.js'
    [W3C (2d1b2b68)] at getAtoms (C:\Program Files\Mobile Center Server\server\appium113\node_modules\appium-remote-debugger\lib\atoms.js:17:13)
    [W3C (2d1b2b68)] at <anonymous>

    Anyone had this error? I dont really know what to do =/

    Thank you @wswebcreation, very useful. I think its a good approach, rely on ios12 tests until ios 13 gets fully supported by appium.
    Roc Itxart Alba
    @wswebcreation Yes Yes I know! I was trying to get a first look to see if our app looked ok! But 90% of my TC are failing, we will do it from the functional side! Thanks anyway for the help! If we can help somehow for it let me know!
    Wim Selles
    Finally I've launch Appium, but unfortunately, always get error "unable to locate element..." using any selectors, when activate Python script. Tap by coordinates works, then trouble not in configuration. Please help me.
    Hi I tried using Appium with desktop application and Appium session is losing connection after the splash screen goes off. I want to inspect the elements after splash screen has gone.
    iOS or Android?
    I had the same behaviour when the app wasn't build for the right architecture
    (on iOS)
    Hello, I would like to to distribute the execution of X cucumber tests among 2 Android devices, I have tried many times but... any idea that could help?
    Roc Itxart Alba
    Selenium Grid?
    Will that allow me to run tests on different devices? (not the same test on all devices)

    Currently I am using Appium, Selenium, Java, TestNG for native app. I am doing automation for iOS and Android and both functionality is same but yes element identifier is different in iOS and android. None of element have same name. Let’s say for login button element identifier is in following way

    For Android @AndroidFindBy(id = "com.abc.bot:id/home_screen_sign_in_btn") private MobileElement signinbtn; For iOS @FindBy(xpath="//XCUIElementTypeButton[@name='Log In']") private WebElement logInButton;

    Apart from that we are using CircleCI and for iOS and Android have different pipeline and different branch too. My question is, should I keep iOS and Android in same repo or different branch. Can someone explain pros and cons please? Should I use same repo?

    Azeez Ashraf
    Anyone to assist on a android tracker project
    hai , did anyone tried appium with GRPC.
    Aionitoaie Andrei
    @hp001 Since the only difference are the element identifiers, I will keep on framework for both platforms and just add a logic to use what you need depending on the platform.