@Ranjithsamalla I am new to appium automation for testing iOS real device, do you have any example on how to setup capabilities. Currently it's like this: "capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME, "XCUITest");
capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "Janny's iPhone");
capabilities.setCapability(IOSMobileCapabilityType.XCODE_SIGNING_ID, "iPhone Developer");
capabilities.setCapability("unexpectedAlertBehaviour", "accept"); capabilities.setCapability("safariAllowPopups", "true"); capabilities.setCapability("autoGrantPermissions", "true"); capabilities.setCapability("autoAcceptAlerts", "true");
Hello! please tell me, in the latest version of the appium it is impossible to find an element (inside the element - numbers) using predicateString
type == 'XCUIElementTypeTextField' && (value CONTAINS '988 109-36-03' || value CONTAINS '922 222-22-22') - does not work
need to somehow look differently now?
because in cases with letters - everything is ok, the element is searched for:
type == 'XCUIElementTypeStaticText' && (value CONTAINS 'Select' || value CONTAINS 'country') - works
Android automated tests suddenly starts failing for Appium 1.15 after few tests
I have the following error stack for the android automation issue:
Selenium::WebDriver::Error::UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to remote server. Original error: Error: read ECONNRESET UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to remote server. Original error: Error: read ECONNRESET at JWProxy.command (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:261:13) at
These scripts were working on older versions of the Appium which proves that the root cause of this error lies in the new version of appium. FYI I have also tried updating the npm, I have uninstalled and reinstalled appium 1.15, tried the caps["automationName"]="appium". Nothing seems to be working. Any suggestion is highly appreciated.
I'd like to use annotations for finding elements by view tag on Android, I am specifying a test ID through this attribute as we cannot use resource ids for targeting using React Native.
It does not seem like @AndroidFindBy currently supports this.
I see MobileBy.ByAndroidViewTag, but I believe this cannot be used with the page object model to initially locate elements.
Is the only workaround an xpath selector (which requires knowing the tag in advance in addition to the view tag)?
adb shell dumpsys window displays
WINDOW MANAGER DISPLAY CONTENTS (dumpsys window displays)
init=960x540 240dpi cur=960x540 app=897x540 rng=540x502-897x850
命令会发现init = cur != app 。appium取到的分辨是app或者是rang的值，能否修改相关设置在启动的时候取到的是cur或是init的值
Hi everyone, I have a case where I need to click on the Activation link in my Inbox - when I am registering to my app... so flow is :
I am retrieving the activation link and when I use driver.url(activationLink) then I am getting server-side error .... does anyone know how to hit the URL with Appium ... ?