How to handle android device notification for android app automation

Ashu05may 2017-09-04 12:57:23 UTC #1

How to handle android device notification for android app automation. Sometimes we need t

o allow or deny android device notifications while executing automation scripts, can anyone please tell me the procedure.

I have attached screenshot of mobile screen with notification.

Aleksei 2017-09-04 13:32:43 UTC #2

@Ashu05may try:

driver.switchTo().alert().accept();

Ashu05may 2017-09-05 06:02:13 UTC #3

@Aleksei - Its not working.

1137 2017-09-05 06:55:50 UTC #4

Hi, do you tried to get allow button ID with uiautomatorviewer

Aleksei 2017-09-05 07:23:00 UTC #5

@Ashu05may next try:


        WebElement allowButton = driver.findElement(MobileBy.id("com.android.packageinstaller:id/permission_allow_button"));
        new TouchAction((MobileDriver) driver).press(allowButton).waitAction(Duration.ofMillis(70)).release().perform();

1137 2017-09-05 10:18:17 UTC #6

allowButton.click();

Ashu05may 2017-09-05 10:25:06 UTC #7

Yes I am getting allow button id and tried clicking allow button but its not working

1137 2017-09-05 10:27:41 UTC #8

do you have appium log for click action?

Ashu05may 2017-09-05 10:45:56 UTC #9

logs which I am getting as below -

ADB] Attempting to kill all uiautomator processes
[ADB] Getting all processes with uiautomator
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“ps”]
[ADB] No uiautomator process found to kill, continuing…
[UiAutomator] Starting UIAutomator
[ADB] Creating ADB subprocess with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“uiautomator”,“runtest”,“AppiumBootstrap.jar”,"-c",“io.appium.android.bootstrap.Bootstrap”,"-e",“pkg”,“com.housejoy.consumer.activity”,"-e",“disableAndroidWatchers”,false,"-e",“acceptSslCerts”,false]
[UiAutomator] Moving to state ‘online’
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] json loading complete.
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
[AndroidBootstrap] Android bootstrap socket is now connected
[ADB] Getting connected devices…
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”]
[AndroidDriver] Screen already unlocked, doing nothing
[ADB] Device API level: 23
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“am”,“start”,"-W","-n",“com.housejoy.consumer.activity/com.housejoy.consumer.activity.SplashScreenActivity”,"-S"]
[ADB] Waiting for activity matching pkg: ‘com.housejoy.consumer.activity’ and activity: ‘com.housejoy.consumer.activity.SplashScreenActivity’ to be focused
[ADB] Possible activities, to be checked: com.housejoy.consumer.activity.SplashScreenActivity, com.housejoy.consumer.activity.com.housejoy.consumer.activity.SplashScreenActivity
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[ADB] Running ‘C:\Android\android-sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“13eb2e35”,“shell”,“dumpsys”,“window”,“windows”]
[ADB] Found package: ‘com.android.packageinstaller’ and fully qualified activity name : ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’
[ADB] Incorrect package and activity. Retrying.
Appium server stopped successfully

Here I can see, pkg looks different so not sure It is trying to click or not.

Aleksei 2017-09-05 10:51:58 UTC #10

@Ashu05may tried suggestion with “com.android.packageinstaller:id/permission_allow_button” tap? OR you have this screen on START driver and thus driver failed to start?

1137 2017-09-05 12:20:55 UTC #11

driver not run
you have error

[ADB] Incorrect package and activity.

test your capabilities

Aleksei 2017-09-05 12:33:21 UTC #12

@Ashu05may if you want to test this on START update caps:

capabilities.setCapability(AndroidMobileCapabilityType.APP_PACKAGE, "com.android.packageinstaller");
capabilities.setCapability(AndroidMobileCapabilityType.APP_WAIT_ACTIVITY, ".permission.ui.GrantPermissionsActivity");

1137 2017-09-05 13:06:46 UTC #13

it looks like activity name is wrong

igal_epshtein 2017-09-05 21:44:41 UTC #14

We found a capability which has helped us.

Set an autoGrantPerrmisions capability to true

Ashu05may 2017-09-06 06:09:03 UTC #15

Thank you very @igal_epshtein, its a nice way. it works.

amarKumar 2017-09-11 08:56:14 UTC #16

@Ashu05may, can you please post your code snippet for the same. I am also facing similar problem as yours.

Ashu05may 2017-11-14 07:38:54 UTC #17

@amarKumar - please find code -

if(ScrRunInterface.equalsIgnoreCase(“realdevice”)){

		capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, "Android");
		capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION, "4.4.4");
		capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME,"Appium");
		capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "ZX1B34GX78");
		capabilities.setCapability(MobileCapabilityType.APP, app.getAbsolutePath());
		capabilities.setCapability(MobileCapabilityType.NO_RESET, false);
        capabilities.setCapability("app-package", "com.abcd.consumer.activity");  
        capabilities.setCapability("app-activity", "com.abcd.consumer.activity.SplashScreenActivity");  
		capabilities.setCapability("autoGrantPermissions","true");  //this code you need to add
		
        driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
		driver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);
        }
	}