Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jean Raymond Daher
    @jeanraymonddaher
    i have tried every syntax in the doc i cannot get to my element
    const versionNumber = await client.$("~testing");
    i got it where testing is the contentDescription
    HURRAY
    Rahul R Pandya
    @Rahul_RPandya_twitter

    Anyone did work on Appium Server with Circle CI?

    So far I installed Appium via the node in CI server, installed mvn dependencies.

    Now when I'm starting appium as a node command

    appium &

    it's now doing anything and skipping that part running my code and throwing exception about the server not started.

    I'm working on for iOS automation and doing in Mac CI image from Circle CI.
    Can anyone help me here, I'm stuck here for the past 5 days.

    sgkanthu
    @sgkanthu
    @Rahul_RPandya_twitter You have to programmatically start and stop server before the test suite is executed
    Are you using screenplay or cucumber framework?
    swatigandhi5
    @swatigandhi5
    Hello team i facing issue with appium for some functionalities in app only for android
    i have logged a bug for more info please refer appium/appium#14107
    IrshaadKKhan
    @IrshaadKKhan
    very basic issue, after installing android studio tools folder is missing like C:\Users\ki_kh\AppData\Local\Android\Sdk, with that not able to work, uiautomatorviewer. Appium version is
    [Appium] Welcome to Appium v1.17.0
    [Appium] Appium REST http interface listener started on 0.0.0.0:4723
    Android Studio version 3.6.1
    Sitansu
    @Sitansu41905876_twitter

    Anyone facing issue in parallel execution after upgrading appium to 1.17.0 and node.js 12.16.1?

    I'm getting the error message:
    Unable to create a new remote session. Please check the server log for more details. Original error: Error forwarding the new session cannot find

    I'm using caps:
    Capabilities {app: /Users/ios/jenkins/workspac..., appWaitActivity: com.xxx.android.activity...., appWaitDuration: 20000, appWaitPackage: com.xxx.android, automationName: UiAutomator2, connectHardwareKeyboard: false, deviceName: Pixel_2_API_27, nativeWebScreenshot: true, noSign: true, platformName: android, platformVersion: 8.1, recreateChromeDriverSessions: true, resetKeyboard: true, shouldUseSingletonTestManager: false, unicodeKeyboard: true}

    The same config was working perfectly with old node.js
    NODE CONFIG:
    {
    "capabilities": [
    {
    "version":"8.1",
    "maxInstances": 10,
    "platformName": "android",
    "platform" : "android",
    "deviceName": "Pixel_2_API_27"
    }

    ],
    "configuration": {
    "cleanUpCycle": 2000,
    "timeout": 30000,
    "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
    "url":"http://localhost:4725/wd/hub",
    "host": "localhost",
    "port": 4725,
    "maxSession": 10,
    "register": true,
    "registerCycle": 5000,
    "hubPort": 4444,
    "hubHost": "localhost"
    }
    }

    NODE Default cap:
    {"udid":"emulator-5554","systemPort":8100}

    Can someone please let me know if anything I need to change for latest node or appium?

    jsa34
    @jsa34
    Hey - just a general question (not a JS expert, so probably something trivial and easy that I just don't know!) - I'm not sure why appium v. 1.17.0 gets appium-windows-driver v.1.8.0, yet the earlier release of appium 1.17.0-beta.1 gets the newer version of appium-windows-driver (v.1.11.0)?
    jsa34
    @jsa34
    Ah - I seem to have answered my own question - npm shrinkwrap has forced the version to 1.8.0...
    A lot of the versions seem to be behind, including the base driver. How can I update these? Otherwise I am stuck on the version 1.17.0-beta.1, despite later releases using older dependencies?
    qait-tarundwivedi
    @qait-tarundwivedi
    can i ask here appium-espresso-driver question here
    ?
    Got response with status 200: {"id":"a8510355-2ee3-40c4-97a2-f45ee8fae429","sessionId":null,"value":null} [debug] [WD Proxy] Matched '/session' to command name 'createSession' [debug] [WD Proxy] Proxying [POST /session] to [POST http://localhost:8300/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"app":"C:\\Users\\Tarundwivedi\\Downloads\\app-debug.apk","automationName":"Espresso","deviceName":"emulator-5554","forceEspressoRebuild":true,"platformName":"Android","showGradleLog":true,"newCommandTimeout":0,"connectHardwareKeyboard":true},"app":"C:\\Users\\Tarundwivedi\\Downloads\\app-debug.apk","automationName":"Espresso","deviceName":"emulator-5554","forceEspressoRebuild":true,"platformName":"Android","showGradleLog":true,"newCommandTimeout":0,"connectHardwareKeyboard":true,"deviceUDID":"emulator-5554","appPackage":"com.**","appWaitPackage":"com.**.dev","appActivity":"com.**.MainActivity","appWaitActivity":"com.**.MainActivity"}],"alwaysMatch":{}}} [debug] [Espresso] [Instrumentation] [STDOUT] io.appium.espressoserver.EspressoServerRunnerTest: [debug] [Espresso] [Instrumentation] [STDOUT] Process crashed while executing startEspressoServer(io.appium.espressoserver.EspressoServerRunnerTest): [debug] [Espresso] [Instrumentation] [STDOUT] java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
    this is issue i am facing
    Shubhojit Bhattacharjee
    @ShubhojitBhattacharjee
    Hi @/all anybody tried logging into Gmail recently via automation script? Looks like it could be done only thru Google APIs and not thru UI automation anymore.
    qait-tarundwivedi
    @qait-tarundwivedi
    Use google API
    jsa34
    @jsa34
    Another quick question... I have winappdriver+appium on the same node as a firefox+selenium node... When passing the desiredcaps for winappdriver, it randomly resolves to either the FF+selenium node or appium
    Here's a gist of a wrong match by the selenium server... https://gist.github.com/jsa34/5a747005af22b85d2f0f88c39f64e30b How can I distinguish explicitly between the requests for selenium server to funnel the requests as expected?
    qait-tarundwivedi
    @qait-tarundwivedi

    Got response with status 200: {"id":"a8510355-2ee3-40c4-97a2-f45ee8fae429","sessionId":null,"value":null} [debug] [WD Proxy] Matched '/session' to command name 'createSession' [debug] [WD Proxy] Proxying [POST /session] to [POST http://localhost:8300/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"app":"C:\\Users\\Tarundwivedi\\Downloads\\app-debug.apk","automationName":"Espresso","deviceName":"emulator-5554","forceEspressoRebuild":true,"platformName":"Android","showGradleLog":true,"newCommandTimeout":0,"connectHardwareKeyboard":true},"app":"C:\\Users\\Tarundwivedi\\Downloads\\app-debug.apk","automationName":"Espresso","deviceName":"emulator-5554","forceEspressoRebuild":true,"platformName":"Android","showGradleLog":true,"newCommandTimeout":0,"connectHardwareKeyboard":true,"deviceUDID":"emulator-5554","appPackage":"com.**","appWaitPackage":"com.**.dev","appActivity":"com.**.MainActivity","appWaitActivity":"com.**.MainActivity"}],"alwaysMatch":{}}} [debug] [Espresso] [Instrumentation] [STDOUT] io.appium.espressoserver.EspressoServerRunnerTest: [debug] [Espresso] [Instrumentation] [STDOUT] Process crashed while executing startEspressoServer(io.appium.espressoserver.EspressoServerRunnerTest): [debug] [Espresso] [Instrumentation] [STDOUT] java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.

    any solution in this

    Hcj Jf
    @Jcjgo_gitlab
    Hi guys
    Hello
    😁😥
    👩🏻‍🚒👩🏻‍🚒👩🏻‍🚒
    Anybody
    Rahul R Pandya
    @Rahul_RPandya_twitter
    @sgkanthu I did try to add in BeforeSuite but in CircleCI it won't work as in Appium I am passing host as localhost. Few forum suggested that Appium need to start from circleci itself from NodeJs so that it can run from it's server rather than local server.
    Roei Adler
    @roitheking1_gitlab
    hi
    i'm trying to run tests on spotify on my phone
    but its always reinstall it
    doing it via webstorm ,fullReset doesn't seem to work
    semenko92
    @semenko92
    Hello guys, please help me
    Appium is now opened an app
    [info] [WD Proxy] Got an unexpected response with status undefined: {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":8100}
    and i have this mistake, and unfortunately I cant to find some solution
    if you know, please advice
    ganeshgunaki
    @GaneshGunaki
    Hi All , anyone got the solution for this >> Cannot get 'xml' source of the current application error #13705
    sgkanthu
    @sgkanthu
    @roitheking1_gitlab set noReset to true
    @Rahul_RPandya_twitter yes, you had to install appium on circleCI server and invoke it in before suite using Appium local service
    pre-requisite: Java, nodejs, Appium installed on circleCI and run the scripts through maven or gradle plugins
    gsai0205
    @gsai0205
    Hi,
    I see the below issue when I try to launch apk app using appium desktop for only android version <=8
    E appium : error while getting field mSSID from object [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&FOREGROUND LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -50] No field mSSID in class Landroid/net/NetworkCapabilities; (declaration of 'android.net.NetworkCapabilities' appears in /system/framework/framework.jar)
    The above log is from adb logcat
    Appium server logs:
    [BaseDriver] Event 'newSessionStarted' logged at 1585607866423 (15:37:46 GMT-0700 (Pacific Daylight Time))
    [MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.quintech.mpers' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command 'C:\Users\GOLISA\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am start -W -n com.quintech.mpers/host.exp.exponent.MainActivity -S' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability
    [MJSONWP] at ADB.startApp (C:\Users\GOLISA\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\lib\tools\apk-utils.js:153:11)
    [HTTP] <-- POST /wd/hub/session 500 33229 ms - 693
    [HTTP]
    [HTTP] --> DELETE /wd/hub/session
    [HTTP] {}
    [HTTP] No route found. Setting content type to 'text/plain'
    [HTTP] <-- DELETE /wd/hub/session 404 1
    prachiy
    @prachiy
    Hello Guys,
    I am facing an issue regarding automation testing.
    i am implementing test cases by using an apk which is implemented by buildozer (backend coding of apk is python and kivy is the gui ). so whenever i am trying to inspect elements of this apk , appium wont allowed me to inspect the single element. it is selecting the whole page of screen. i think appium is considering whole apk as a single element that's why it wont allow me to inspect single element.
    but is this right issue , why it doesn't allow me to inspect the single element ,please guys help.
    lfalkner
    @lfalkner
    Hello, I'm looking to test a react-native application using appium and saucelabs. I've noticed that the JS bundle never seems to resolve in saucelabs. I'm using a debug APK with release JS bundle. The result is that a remote test run shows as a blank white screen for the duration of the test How would I resolve this?
    rdtx2015
    @rdtx2015

    Hi all, I'm using Python-Appium. I have my main test.py and put my locators to locators.py. Some of these locators have index [0] and some have brackets. When I python run the code, i'll get a parser error from jaxon.. [debug] [W3C (8d379b84)] Encountered internal error running command: io.appium.uiautomator2.common.exceptions.InvalidSelectorException: java.lang.IllegalArgumentException: Unable to compile '["xpath","(\/\/android.view.ViewGroup[@content-desc='NO THANKS'])"]'. See Cause.

    the selector should be //android.view.....

    Any help is appreciated

    this is my locators.py (partial)

    All the Locators

    from selenium.webdriver.common.by import By

    class Locators():

    # --- Location Services Splash Page ---
    NO_THANKS = (By.XPATH, "(//android.view.ViewGroup[@content-desc='NO THANKS'])")

    in my test.py i'll import locators.. then use locators.NO_THANKS like so.. self.driver.find_element_by_xpath(Locators.NO_THANKS).click()