Hi,

I am new to Appium automation. I am stuck right now with identifying the elements of login page. The app which I am testing is available in Google Play store “SmartView Quality”. When I am using command "System.out.println("name of context is “+ driver.getContextHandles());” , then I am getting output sometime as “name of context is [NATIVE_APP]”.

But sometime the same command give output as “name of context is [NATIVE_APP, WEBVIEW_chrome]”. So I am confused whether the app is native or hybrid.

Kindly help me with finding the elements of login page. I am using Appium Desktop 1.7.0 with Java client 6.1.0. I am testing it in real device “Samsung S7 Edge”

I tried to find the elements using Appium Inspector (Screenshot attached).

appium inspector new.png1366x768 113 KB

I am getting following locators:

id = Text1

class = android.widget.EditText

package = at.ondot.qmapp

But still unable to locate element using these locators

Here is my code:

public class SamsungOldQual

{

@Test

public void test_qual() throws InterruptedException {

AppiumDriver driver = null;

//AndroidDriver driver =null;

DesiredCapabilities caps = new DesiredCapabilities();

caps.setCapability(“deviceName”, “Phone”);

caps.setCapability(“udid”, “31603cdcf39*”);

caps.setCapability(“appPackage”, “at.ondot.qmapp”);

caps.setCapability(“appActivity”, “at.ondot.qmapp.MainActivity”);

caps.setCapability(“noReset”, “true”);

/*caps.setCapability(MobileCapabilityType.BROWSER_NAME, “Chrome”);

caps.setCapability(“autoWebview”, “true”);

caps.setCapability(“chromedriverExecutable”, “D:\Browser Drivers\chromedriver_win32_new\chromedriver.exe”);

*/

try {

driver = new AndroidDriver(new URL(“http://0.0.0.0:4723/wd/hub”), caps);

} catch (MalformedURLException e) {

System.out.println(e.getMessage());

}

driver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);

System.out.println("Context count is "+driver.getContextHandles().size());

System.out.println("name of context is "+ driver.getContextHandles());

/*driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

driver.findElementById(“at.ondot.qmapp:id/Password1”).sendKeys(“aaa”);

driver.context(“WEBVIEW_chrome”);*/

WebDriverWait wait = new WebDriverWait(driver, 10);

wait.until(ExpectedConditions.visibilityOfElementLocated(By.className(“android.widget.EditText”))).sendKeys(“abcd”);

//driver.findElement(By.id(“Text1”)).sendKeys(“yusuf”);

}

}

Thanks!! I will now try to use Xpath for finding elements from page.

Both devices are on different android version. Real device is on android version 8.0.0 and emulator is on Android version 8.1.0. The odd behavior is I am unable to see the webview in real android device, so unable to access the element. But in emulator, I am able to see the webview and can access the element with their IDs. Don’t know why this strange behavior is happening. It might be due to different android version, but not sure.

For real android device(8.0), driver.context mostly gives output as “NATIVE_APP” only and rarely gives “WEBVIEW_chrome”.
But emulator (8.1) always gives output as “NATIVE_APP, WEBVIEW_chrome, WEBVIEW_at.ondot.qmapp”

That’s why I guess, I am unable to locate element in real android device. I don’t know why the real android device is unable to locate webview. Do you know any resolution for it?

Hi Weyler,
Could you please help me with 1 issue which I am facing while using sendKeys to a userName text field.
I am able to access the element and can perform click on that web element. But I am unable to use sendKeys and getting error message as "An unknown server-side error occurred while processing the command. Original error: unknown error: cannot focus element"
I tried below methods:
WebElement ele=driver.findElement(By.id(“userName”));
ele.click();
Thread.sleep(3000);
ele.sendKeys(“yusuf”);

I also tried driver.findElement(By.id(“userName”)).sendKeys(“yusuf”);

But none of them worked.

I am working on Emulator with android version 8.1 , with chrome version= 61, Chrome driver version 2.33 and also 2.34, Appium 1.9.0 and Java Client 6.1.0.

Could you please help me how to resolve this issue?
Thanks

Hi Weyler,
I tried with driver.hideKeyboard(); But it didn’t work. My userName text field is non-focusable with or without the keyboard.
With Keyboard:

image.png939x501 31.4 KB

Without keyboard

image.png896x476 17.5 KB

I think FOCUS=FALSE might be the reason sendKeys not working. If yes then how to resolve it?

Also 1 interesting which I notice is that after clicking somewhere else in the userName field focus changes to true. See below screenshot:

image.png902x499 18.7 KB

Kindly suggest how to rectify it so that my sendKeys() starts working.

Thanks!

Hi Weyler,
Yes, there was View over Edit Text. That’s why focus was false, I guess so.
When I tried to access the element by:
driver.findElement(By.id(“userName”)).sendKeys(“yusuf”);
It didn’t work.

And when I tried to point my xpath to focus field, it worked fine
driver.findElementByXPath("//*[@id=‘userName’]/input").sendKeys(“check”);

Issue is resolved now. Thanks a lot for your help!