Need to verify keyboard is shown on device screen(android/ios).
Not able to identify keyboard element on screen. So tried using the below method. But its not working.
isKeyboardShown() - it is showing as undefined for the type of appium driver.
using appium version - 7.4.1
<groupId>io.appium</groupId>
<artifactId>java-client</artifactId>
<version>7.4.1</version>
Is there any other appium method or way to check this?
isKeyboardShown is the right way to check it and works on both Android and iOS platform.
In order to use it, you need to properly create an instance of driver (AndroidDriver/iOSDriver):
driver = new AndroidDriver(appiumURL, capabilities);
boolean isDisplayed = driver.isKeyboardShown();
isKeyboardShown() is the correct way to do it, you just need to cast your driver, in case you are using an AppiumDriver to AndroidDriver or IOSDriver depending on the case, like:
((AndroidDriver)driver).isKeyboardShown();
((IOSDriver)driver).isKeyboardShown();
Try declaring the keyboard container as an element and verify it with isDisplayed()
My simulator keyboard is not displayed when I run my test cases from automation. I keep getting the below error.
Original error: Error Domain=com.facebook.WebDriverAgent Code=1 "Keyboard is not present" UserInfo={NSLocalizedDescription=Keyboard is not present}
When my automation code opens simulator, In simulator->Harward->keyboard->Connect Hardware keyboard is unchecked and I am not able to check that.
And when I open simulator normally I get the simulator keyboard and the option Connect hardware Keyboard is also selected by default
Can anyone help me out here.
Its a known WebDriverAgent issue: https://github.com/facebook/WebDriverAgent/issues/574
Try to update to latest Appium server 1.9.1 to use latest version of WebDriverAgent.
If it won't help, follow suggestion from the last comment on github issue:
Before tests run bash script defaults write com.apple.iphonesimulator ConnectHardwareKeyboard -bool no
Add turn off hardware keyboard as it seems to cause failures occasionally
error occurs when you use ios simulator.
To solve this use below command for enabling keyboard.
1.Restart your Xcode if it's already open. Then use below keys.
For opening and closing keyboard you can use below shortcuts.
cmd + k
If first option doesn't work then set below capabilities in your script.
2.
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("Connect Hardware Keyboard", true);
OR
(capabilities.setCapability(IOSMobileCapabilityType.CONNECT_HARDWARE_KEYBOARD, true)
I resolved this on iOS for Mobile app automation using Appium
Set the capability to not refer to the hardware keyboard
cap.setCapability("connectHardwareKeyboard", false);
While executing the case, where you need to access the keyboard use
driver.findElementByXPath("****** ").sendKeys("Text")
After getting the input on the field, dismiss the keyboard
driver.hideKeyboard()
iOS:Real Device
Uninstall if you have installed any third party keyboards, keep only the default keyboard on the device.
Re run the same code. It should work now
Uninstalling Keyboards: Settings ->General -> KeyBoards-> Edit
Under the:
chrome://flags
I didn't find
--enable-precise-memory-info
Trying to run with:
ChromeOptions options = new ChromeOptions();
options.AddArguments("--enable-precise-memory-info");
also had no success, values are rounded.
Is it even possible?
Let me know if you need more details on this issue
Note: it's not about desktop, mobile chrome browse only!
One way of doing this is with adb
adb -s $deviceId shell am start -n com.android.chrome/com.google.android.apps.chrome.Main argv --args='--enable-precise-memory-info'
to obtain device id:
adb devices
But it wouldn't save flag for the next session, and if you are trying to open it with SeleniumWebDriver probably it should be done with DesiredCapabilities through adding ChromeOptions... but it's still a question how to do it
Currently an Appium 1.7.1 issue.
Follow fix progress here:
https://github.com/appium/appium/issues/9838
I have to automate an Android application, I am doing the same through Appium.
The problem I am facing is after launching the Appium server, the app is getting installed in the emulator 4.4.2. To inspect the element I am using UIAutomatorviewer which comes default with SDK. But while inspecting the element of the app, I am getting the error:
Error obtaining UI hierarchy
Reason:Error while obtaining UI hierarchy XML file.com.android.ddmlb.SynchException.Remote object doesn't exist.
I tried to find the solution so that I can inspect the element so that I can script, but in vain.
Can someone please tell how to fix the issue so that I can inspect elements?
Is there any other way I can inspect element in the app apart from using UIAutomator viewer?
After my tryst with the uiautomator viewer i came to know that we get the error only when:
appium server is running and we try to capture the screenshot using uiautomatorviewer.
So, whenever you want to use uiautomatorviewer make sure that server is in stopped state.
I fixed the same issue by using following methods.
(1) Connect your Android device to your development machines;
(2) Go to command line in terminal or DOS command line for Windows;
(3) Using "adb shell" into your Android devices;
(4) Change the user to root by input "su root" in command line;
(5) Change the access right to /data/local/tmp by input "chmod 777 /data/local/tmp";
(6) Go back to uiautomatorviewer and do screen shot again, the error should be gone;
I guess there are some file can't be access if it doesn't own right in /data/local/tmp.
Make sure everything on your screen is static. And flashing input cursor is also not allowed. Any painting actions will stop uiautomator from dumping current UI.
You can test by using following adb command:
adb shell uiautomator dump /data/local/tmp/uidump.xml
if the message ERROR: could not get idle state. appears, you are suffering from this issue.
See lines 87 & 101 of DumpCommand:
try {
...
uiAutomation.waitForIdle(1000, 1000 * 10);
...
} catch (TimeoutException re) {
System.err.println("ERROR: could not get idle state.");
return;
}
Easiest solution..
Restart the device. Restart uiautomatorviewer.
Worked like a charm for me .... :P
Stop the Appium Server. Then try again. It works.
I had the same problem because I used "adbd insecure". So I just disabled "adbd insecure", and reload uiautomatorviewer, everything is OK.
In case of rooted devices: Enable the root access in developer options for adb. Restart adb as root
I have spent over a week to resolve this issue. When you connect your device and using ASM 3.0, when screen is projected open the UIAutomator to capture the current android screen. Without Appium it should capture. For use Android Studio instead of android sdk. Uninstall and reinstall Android Studio. It is working perfect for me now.
Answer to your question #2
You can inspect Android app directly from your real Android device.
You need to:
Connect Android device to your computer/laptop
Go to Android device Settings -> Enable Developer Options and Android debbuging
Please see here:
Start the app you wish to inspect in your Android device
Open up the Chrome browser on your computer/laptop and do a right click -> More Tools -> Inspect devices -> Click on your device -> (Click on Android device OK to authorize) -> Click Inspect
Please see here:
That's it. Hope it helps!
I got also the same issue (Also if Appium Server was not running). After switch, OFF / ON USB-Debugging was working for me.
I got it resolved
I closed the Appium Server running on my machine and opened it again.
Later open uiautomater, and it worked for me
The one that works is in this path:
Android/Sdk/tools/bin/uiautomatorviewer
Paste this in your terminal and it will run automator that works
we have to use device which has API level morethan 17 or jelly bean
Way to bypass the ERROR:
could not get idle state.
By using uiautomator to get uix and screenshot.
public class DeviceMethods extends UiAutomatorTestCase {
public void dump(){
try {
getUiDevice().dumpWindowHierarchy("window_dump.uix") ;
getUiDevice().takeScreenshot(new File("/data/local/tmp/window_dump.png"));
} catch (Exception e) {
}
}
you need to create the uiautomator jar and push it to /data/local/tmp
use this tutorial on how to use uiautomator
after you get the files just open them in uiautomatorviewer
What worked for me:
stop appium
open an emulator device (tested with Android 7.1.1)
go into settings > developer options > Enable view attribute inspection
open a shell on the computer, cmd or terminal depending on your OS
enter the following commands:
adb shell
su
cd /data
cd /local
chmod 777 tmp
start uiautomatorviewer
take an xml screenshot
"su chmod 777 /data/local/tmp" didnt work for me so I drilled down and it worked. I assume that you have to do this in an emulator and not a physical device unless the device is rooted. ¯ \ _ (ツ)_/¯
Lotsa Luck!
This happens because adb is using port and it's blocked by appium server.
I have found out best solution for this
Kill the adb.exe from taskbar processes and try launching uiautomatorviewer again
Check whether you have enabled these under "developer options" in the phone.
Verify apps via USB
View attribute inspection
USB debugging
1) stop appium Server
2) open an emulator device
3) go into settings > developer options > Enable view attribute inspection
4) developer options in invisible? Go into settings > Tap on About device/phone > Scroll down till the last option(Build number) > Continuously Tap on "Build number" for 7 times > you should get an Toast message "You're a developer" > come back from that screen > Go back into settings > Now you should see developer options Tap on it > Enable view attribute inspection
5) You should no more get this error message
Why don't you use appium inspector instead? You can download it and follow instructions from here
try switching Off and then ON the USB debugging option.. this work for me
I am trying to record iOS automated Tests using Appium Inspector by instructions using tutorial..
http://www.youtube.com/watch?v=Hv9A9WfYF4g
I have my app on workspace. I built it using iphonesimulator7.0 which showed a sucess message then correctly set the path to the built app on appium inspector. But when i click Launch it shows the error.
Appium Error:main.js: error: Unrecognized arguments: --no-session-override
on its console..Any idea what might be the problem.
PS:Am using appium for the first time
above is the screenshot that i get when i click launch button..
Please check whether Override Existing Sessions checkbox is checked or not. It should be checked.
Appium -- > Preferences ---> General