Showing posts with label Android. Show all posts
Showing posts with label Android. Show all posts

Monday, September 19, 2016

How to fix INSTALL_FAILED_NO_MATCHING_ABIS error while installing apk in Genymotion

Genymotion is a faster android emulator(Virtual Android Environment) built on x86 and Virtualbox. Its performance is much better than the Google's Android SDK Emulator as it is not an ARM emulator.

However in the latest Genymotion updates, they have removed both the ARM Translation and Google Play Apps. So, when you are trying to install an app which has native libraries but doesn't have a native library for your CUP architecture. For example, if an app is compiled for armv7 and we try to install it on the emulator that uses the Intel architecture instead, it will not work and will give you an error INSTALL_FAILED_NO_MATCHING_ABIS .

To make the app to work in both the CPU architectures, we need to install the ARM Translation.
Steps for installation:
  1. Download the ARM Translation from the link Genymotion-ARM-Translation_v1.1.zip
  2. Open the Genymotion emulator and be in the home screen
  3. Install the downloaded ARM Translation. To installed just you need to drag and drop the zip file in the Genymotion emulator window. Click 'Ok' if it prompts after the 'file transfer in progress' operation
  4. Restart the Genymotion emulator(using adb or close and open)
Now install the application(by using adb or just drag and drop the apk into the emulator window), you shouldn't see any error such as INSTALL_FAILED_NO_MATCHING_ABIS and the application should be installed successfully.

Hope it helps!

Monday, January 18, 2016

Checking if android emulator or device is running

We can check if an android device or an emulator is attached(plugged in) or running before we start using the attached device.

Command line:
We can check the following command to check list of attached devices
adb devices
The above command will provide you the list of attached devices.
Example output,
List of devices attached 
192.168.56.101:5555 device
emulator-5554 device 
Programmatically:
We can do this check programmatically also as below
private static String sdkPath = "/Applications/adt-bundle-mac-x86_64-20140702/sdk/";
private static String adbPath = sdkPath + "platform-tools" + File.separator + "adb";
/**
 * Checks if an emulator or a device is already launched or plugged in
 * 
 * Example: 

 * List of devices attached 

 * 192.168.56.101:5555 device 

 * emulator-5554 device
 * 
 * @return
 */
public static boolean isEmulatorOrDeviceRunning() {

 try {
  String[] commandDevices = new String[] { adbPath, "devices" };
  Process process = new ProcessBuilder(commandDevices).start();

  BufferedReader inputStream = new BufferedReader(new InputStreamReader(process.getInputStream()));

  String output = "";
  String line = null;
  while ((line = inputStream.readLine()) != null) {
   System.out.println(line);
   output = output + line;
  }
  if (!output.replace("List of devices attached", "").trim().equals("")) {
   return true;
  }
 } catch (Exception e) {
  e.printStackTrace();
 }
 return false;
}
If the device or emulator is just plugged in or launched, it may not be ready though its running, so wait till it gets ready by the post Waiting for android emulator to be ready

Waiting for android emulator to be ready

When we start android emulator(or is already running), we need to ensure its ready for testing and is responding. 

Command line:
This can be ensured by following commands:
adb shell getprop dev.bootcomplete 
We need to wait for the above command till it returns 1
adb shell getprop sys_bootcomplete 
We need to wait for the above command till it returns 1
adb shell getprop init.svc.bootanim
We need to wait for the above command till it returns "stopped"
Note: 1st and 3rd commands are important to check. Maximum case 2nd command will be ready.

Programmatically:
Also can be done programmatically,
private static String sdkPath = "/Applications/adt-bundle-mac-x86_64-20140702/sdk/";
private static String adbPath = sdkPath + "platform-tools" + File.separator + "adb";
/**
 * Waits for the emulator to be ready
 */
public static void waitForEmulatorToBeReady() {
 try {
  String[] commandBootComplete = new String[] { adbPath, "shell", "getprop", "dev.bootcomplete" };
  Process process = new ProcessBuilder(commandBootComplete).start();
  BufferedReader inputStream = new BufferedReader(new InputStreamReader(process.getInputStream()));

  // wait till the property returns '1'
  while (!inputStream.readLine().equals("1")) {
   process.waitFor(1, TimeUnit.SECONDS);
   process = new ProcessBuilder(commandBootComplete).start();
   inputStream = new BufferedReader(new InputStreamReader(process.getInputStream()));
  }

  String[] commandBootAnim = new String[] { adbPath, "shell", "getprop", "init.svc.bootanim" };
  process = new ProcessBuilder(commandBootAnim).start();
  inputStream = new BufferedReader(new InputStreamReader(process.getInputStream()));

  // wait till the property returns 'stopped'
  while (!inputStream.readLine().equals("stopped")) {
   process.waitFor(1, TimeUnit.SECONDS);
   process = new ProcessBuilder(commandBootAnim).start();
   inputStream = new BufferedReader(new InputStreamReader(process.getInputStream()));
  }

  System.out.println("Emulator is ready to use!");
 } catch (Exception e) {
  e.printStackTrace();
 }
}
You can ensure if an emulator or device is already running before using the above method or commands by the post Checking if android emulator or device is running

Stop or kill android emulator programmatically and from command line

If you are looking for starting(or launching) android emulator from command line or programmatically, please refer my post start or launch android emulator programmatically and from command line
Sometimes we need to stop our running emulator(s) to start a new emulator or to execute tests in a real devices or because of some other situation. To stop a running android emulator we can do by following ways:

Manually stop emulator:
Open the running emulator > click on the close button(red cross icon in the top menu bar). The emulator should be closed.

Stop emulator from command line:
Use the following command to kill all running emulators.
adb emu kill
Stop emulator programmatically:
We can close emulators programmatically also. The following code will close all the running emulators.
private static String sdkPath = "/Applications/adt-bundle-mac-x86_64-20140702/sdk/";
private static String adbPath = sdkPath + "platform-tools" + File.separator + "adb";
/**
 * Kills all running emulators
 */
public static void closeEmulator() {
 System.out.println("Killing emulator...");
 String[] aCommand = new String[] { adbPath, "emu", "kill" };
 try {
  Process process = new ProcessBuilder(aCommand).start();
  process.waitFor(1, TimeUnit.SECONDS);
  System.out.println("Emulator closed successfully!");
 } catch (Exception e) {
  e.printStackTrace();
 }
}
Hope it helps!

Start or launch android emulator programmatically and from command line

For executing android tests in android emulator(AVD), we need to start it and ensure its running before our test starts executing. This post will explain you how can we start android emulator from code and from command line(mainly these will be helpful when we configure our test execution jobs in CI tools like Jenkins)

Manually launching emulator:
This can be easily opened from the IDE(eclipse if you are using adt bundle)
Open eclipse > select menu "Windows" > Select "Android Virtual Device Manager" >  select the AVD you want to launch(create an AVD if not yet created) > Click on "Start..." button > Click "Launch" button to launch the emulator > The emulator will launch in a moment

Launching emulator from command line:
The following command will launch the android emulator. Please ensure you have SDK installed and path has set.
emulator -avd <avd_name>
For example,
emulator -avd AVD_for_Nexus_4_by_Google
You can start with many options, for more information please refer here.

Launching emulator programmatically:
You can achieve this in code too. You can execute this script using ProcessBuilder class in java as below.
private static String sdkPath = "/Applications/adt-bundle-mac-x86_64-20140702/sdk/";// or for windows D:/Android/adt-bundle-windows-x86_64-20140702/sdk/
private static String adbPath = sdkPath + "platform-tools" + File.separator + "adb";
private static String emulatorPath = sdkPath + "tools" + File.separator + "emulator";
Please make sure to change the value of "sdkPath" variable to your SDK installation directory.
The following code will start an emulator with the provided AVD name.
 
/**
 * Starts an emulator for the provided AVD name
 * 
 * @param nameOfAVD
 */
public static void launchEmulator(String nameOfAVD) {
 System.out.println("Starting emulator for '" + nameOfAVD + "' ...");
 String[] aCommand = new String[] { emulatorPath, "-avd", nameOfAVD };
 try {
  Process process = new ProcessBuilder(aCommand).start();
  process.waitFor(180, TimeUnit.SECONDS);
  System.out.println("Emulator launched successfully!");
 } catch (Exception e) {
  e.printStackTrace();
 }
}
The 3 minute(180 sec) wait in the above code is to wait for the emulator which can be decreased or increased depending upon your system performance. 

If you want to stop or kill your running emulator, please refer my post Stop or kill android emulator programmatically and from command line

Tuesday, December 15, 2015

Set up Appium for beginners (Android & iOS)

Appium is an open source test automation tool to automate native and hybrid mobile apps. For more details about the tool please go through http://appium.io/

Below are the steps for setting up Appium in your test machine (with Eclipse):

Step-1: Install Java
Ensure you have java installed in your machine. If not installed, please install it as per the below steps.
  1. Download latest java from http://www.oracle.com/technetwork/java/javase/downloads/index.html or from http://java.com/en/download/
  2. Double click on the downloaded file and follow the instructions to finish the installation. Please note the installation directory.
  3. Once java is installed, you need to set the path for java as follows
    For path setting in Windows,
    For path setting in Mac, please follow the below instructions
    • Look for ".bash_profile" in your home folder
    • If hidden files are not shown by default, you won't see this file. So execute below 2 command to show hidden files in mac
    defaults write com.apple.finder AppleShowAllFiles YES
    killall Finder
    
    • Start up Terminal
    • Type "cd ~/" to go to your home folder
    • Type "touch .bash_profile" to create your new file if ".bash_profile" doesn't exist
    • Edit ".bash_profile" with your favorite editor (or you can just type "open -e .bash_profile" to open it in TextEdit.
    • Update the file with the installed java home location as below example format
    set JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
    export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
    export PATH=$PATH:${JAVA_HOME}:${JAVA_HOME}/bin
  4. To test java installation, open your command prompt(in windows) or terminal(in mac) and enter
  5. java -version
    • You will get the version of java you have installed as below example,
    java version "1.8.0_71"
    Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
    Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)
    
Step-2: Download ADT bundle for Eclipse(Only if you want to test android application, not required for iOS application testing)
  1. You can download adt bundles (e.g. version 2014-07-02) from below sites:
  2. windows 32: https://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
    windows 64: https://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
    Mac 64: https://dl.google.com/android/adt/adt-bundle-mac-x86_64-20140702.zip
    Linux 86: https://dl.google.com/android/adt/adt-bundle-linux-x86-20140702.zip
    Linux 64: https://dl.google.com/android/adt/adt-bundle-linux-x86_64-20140702.zip
  3. Extract the downloaded zip file and extract them to a safe folder. Inside the folder you will find 2 folders. One is eclipse and another with SDK for android
  4. Set the PATH for android SDK. 
    • In Windows, create a system variable ANDROID_HOME and append the "tools" and "platform-tools" locations in PATH environment variable
    ANDROID_HOME=D://android/adt-bundle-windows-x86_64-20140702/sdk
    PATH=%ANDROID_HOME%//tools;%ANDROID_HOME%//platform-tools;
    • In Mac, append the below in ".bash_profile" file
    set ANDROID_HOME=/Applications/adt-bundle-mac-x86_64-20140702/sdk
    export ANDROID_HOME=/Applications/adt-bundle-mac-x86_64-20140702/sdk
    export PATH=$PATH:${JAVA_HOME}:${JAVA_HOME}/bin:${ANDROID_HOME}/tools:${ANDROID_HOME}/platform-tools
  5. Then you need to test sdk installation in the system. To do this, navigate to "platform-tools" directory inside sdk from command line or terminal and type command
  6. adb devices
    • You should get the below message in the terminal or command prompt
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached 
    
    • If you won't see "List of devices attached" message in the output, you might not set the sdk path properly. Please check the steps once again and correct the missing ones to get it properly.
  7. If you want latest android versions, open SDK manager and update the required android versions.
Step-3: Install Appium
  1. Open terminal and type below command
  2. sudo chown -R `whoami` /usr/local
    • Click the enter key and enter system password if it asks
    • Note: Sometimes in Mac system, you may get command not found error. Then please ensure the below is added in your ".bash_profile". You can addend at the end of file.
    export PATH=$PATH:/usr/sbin
    export PATH=$PATH:/usr/bin
    export PATH=$PATH:/usr/local/bin
  3. Next type the below command
  4. ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
    
    • Then click enter and follow the instructions to continue (provide system password is prompts)
    • Note: In mac machine, it may prompt for any dependant software (e.g. xcode) then please click on install, if you want to test an iOS application. If you want to test an android application you don't need to install it.
  5. Next install node by below command
  6. brew install node
    
    • and click enter. It downloads some files and installs them
    • To see node is installed successfully, please type below in command line
    node -v
    
    •  and click enter then you can see the version of the node installed
  7. Install appium by executing below command
  8. npm install -g appium
    
    •  and click enter, it will take some time to download all the appium related installations. 
  9. To test appium installation, use below command
  10. appium
    
    •  and click enter, it will show the version of appium running and will start the appium server from command line.
    info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
    info: Appium REST http interface listener started on 0.0.0.0:4723
    info: Console LogLevel: debug
    
    Now you can proceed with developing/executing android or iOS automated tests using appium.
    Happy testing!!!

Wednesday, October 21, 2015

Hide Soft Keyboard in Android Emulator/Device

There are multiple strategies for hiding the keyboard:

Method -1
There is a direct method available in AndroidDriver (or if you are using appium for mobile test automation, this method is availale in AppiumDriver too)
For example,
AndroidDriver<WebElement>  driver = new AndroidDriver<WebElement>(
    new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
driver.hideKeyboard();

Method-2
You can hide soft keyboard completely(or only for some test specific) by passing the following property to the desired capabilities as below:
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("unicodeKeyboard", "true");

Method-3
You can hide by clicking different android keys like "Done" or "Back". Here is an example of hiding soft keyboard using BACK key.
driver.pressKeyCode(AndroidKeyCode.BACK);
In some older versions of AndroidDriver you can find below method
((AndroidDriver) driver).sendKeyEvent(AndroidKeyCode.BACK);

Method-4
You can go back by using following code, which will hide your soft keyboard
driver.navigate().back();
This you need to call only after entering text into edit field. For some views or activities, it may go back to the previous activity.

Method-5
You may try the below if it works for you. In some cases this doesn't work well.
HashMap keycode = new HashMap();
keycode.put("keycode", 4);
((JavascriptExecutor)driver).executeScript("mobile: keyevent", keycode);
Method-6
If you have android application code base integrated with your android test base, you can use the below code which will perform based on your current activity.
public void hideSoftKeyboard(Activity activity) {
  InputMethodManager imm = (InputMethodManager)
  activity.getSystemService(Context.INPUT_METHOD_SERVICE);
  imm.hideSoftInputFromWindow(view.getWindowToken(), 0);
}

Monday, October 12, 2015

Start and Stop Appium Server Programmatically

Pre-requisites:
I assume you have installed the followings in your machine already.
Appium is downloaded (latest from here) and setup properly as mentioned here.
Java Development Kit(JDK) is downloaded(refer here) and installed in your machine.

How to Start or Stop appium server programmatically?
Please refer the below class for detailed usage, Hope it is self explanatory.

Method-1:
package appium.base;

import java.io.File;

import io.appium.java_client.service.local.AppiumDriverLocalService;
import io.appium.java_client.service.local.AppiumServiceBuilder;

/**
 * This page models Appium server
 * 
 * @author A. K. Sahu
 *
 */
public class AppiumServer {

 String appiumInstallationDir = "C:/Program Files (x86)";// e.g. in Windows
 //String appiumInstallationDir = "/Applications";// e.g. for Mac
 AppiumDriverLocalService service = null;

 public AppiumServer() {
  File classPathRoot = new File(System.getProperty("user.dir"));
  String osName = System.getProperty("os.name");

  if (osName.contains("Windows")) {
   service = AppiumDriverLocalService.buildService(new AppiumServiceBuilder()
     .usingDriverExecutable(new File(appiumInstallationDir + File.separator + "Appium" + File.separator + "node.exe"))
     .withAppiumJS(new File(appiumInstallationDir + File.separator + "Appium" + File.separator
       + "node_modules" + File.separator + "appium" + File.separator + "bin" + File.separator + "appium.js"))
     .withLogFile(new File(new File(classPathRoot, File.separator + "log"), "androidLog.txt")));

  } else if (osName.contains("Mac")) {
   service = AppiumDriverLocalService.buildService(new AppiumServiceBuilder()
     .usingDriverExecutable(new File(appiumInstallationDir + "/Appium.app/Contents/Resources/node/bin/node"))
     .withAppiumJS(new File(
       appiumInstallationDir + "/Appium.app/Contents/Resources/node_modules/appium/bin/appium.js"))
     .withLogFile(new File(new File(classPathRoot, File.separator + "log"), "androidLog.txt")));

  } else {
   // you can add for other OS, just to track added a fail message
   Assert.fail("Starting appium is not supporting the current OS.");
  }
 }

 /**
  * Starts appium server
  */
 public void startAppiumServer() {
  service.start();
 }

 /**
  * Stops appium server
  */
 public void stopAppiumServer() {
  service.stop();
 }
}

Usage of this class:
AppiumServer service = new AppiumServer();

// Starts appium server
service.startAppiumServer();

// ... your tests are here. 

// Stops appium server
service.stopAppiumServer();
Note: You can call start appium server in the @BeforeSuite configuration method and stop appium server at @AfterSuite configuration methods.

With the above approach of starting appium server, you can get total android log in the provided log file i.e. "androidlog.txt" file inside "log" directory of your project root directory

Method-2
Here is an another way of starting and killing appium server programmatically using command line executions with java's ProcessBuilder class. Refer below class for more details.
Define the below properties and change as per your appium installation.
 String appiumInstallationDir = "C:/Program Files (x86)";
 String appiumNode = appiumInstallationDir + File.separator + "Appium" + File.separator + "node.exe";
 String appiumNodeModule = appiumInstallationDir + File.separator + "Appium" + File.separator + "node_modules"
   + File.separator + "appium" + File.separator + "bin" + File.separator + "Appium.js";
 String appiumServicePort = "4723";
Execute the start and stop commands like we do from command line but here with using java's ProcessBuilder class.
 /**
  * Starts appium server
  */
 public void startAppiumServer() {
  executeCommand("\"" + appiumNode + "\" \"" + appiumNodeModule 
                      + "\" " + "--no-reset --local-timezone");
 }

 /**
  * Stops appium server
  */
 public void stopAppiumServer() {
 executeCommand("cmd /c echo off & FOR /F \"usebackq tokens=5\" %a in" 
  + " (`netstat -nao ^| findstr /R /C:\""
  + appiumServicePort + "\"`) do (FOR /F \"usebackq\" %b in"
  + " (`TASKLIST /FI \"PID eq %a\" ^| findstr /I node.exe`) do taskkill /F /PID %a)");
}
You may need the below class for executing a command line command. This you can do using Runtime.getRuntime().exec(command) also, but I would suggest to use ProcssBuilder as this is recommended.
 /**
  * Executes any command for Windows using ProcessBuilder of Java You can
  * change the first input parameter of ProcessBuilder constructor if your OS
  * is not windows operating system
  * 
  * @param aCommand
  */
 public void executeCommand(String aCommand) {
  File currDir = new File(System.getProperty("user.dir"));
  String line;
  try {
   ProcessBuilder probuilder = new ProcessBuilder("CMD", "/C", aCommand);
   probuilder.directory(currDir);
   Process process = probuilder.start();

   BufferedReader inputStream 
        = new BufferedReader(new InputStreamReader(process.getInputStream()));
   BufferedReader errorStream 
        = new BufferedReader(new InputStreamReader(process.getErrorStream()));

   // reading output of the command
   int inputLine = 0;
   while ((line = inputStream.readLine()) != null) {
    if (inputLine == 0) {
     System.out.printf("Output of the running command is: \n");
    }
    System.out.println(line);
    inputLine++;
   }

   // reading errors from the command
   int errLine = 0;
   while ((line = errorStream.readLine()) != null) {
    if (errLine == 0) {
     System.out.println("Error of the command is: \n");
    }
    System.out.println(line);
    errLine++;
   }

  } catch (IOException e) {
   System.err.println("Exception occured: \n");
   System.err.println(e.getMessage());
  }
 }

With the above method, the server log will be printed in the console as I kept standard output and error statements. You can change to trace these log in a log file if you need it.

Hope it is useful !!