Android M and permissions

willosser · January 13, 2016, 5:37pm

@vrunoa, that looks great.

Back to my original point, I believe it would be preferable to have a capability that installs the application with all permissions by default. I’ve extended the use of adb on our project so I can do just that.

vrunoa · January 13, 2016, 6:06pm

@willosser
On Android 6 you can no longer use all the dangerous permissions by default. Every android app should use the ActivityCompat.requestPermissions before use any dangerous API.
For example; if you try to use the camera without the write_external permission accepted by the user, the camera will silently fail by giving you a null pointer to the taken picture. It can also crash with other permission not accepted.

The request permission flow is quite important now because you may want to take different action if the user did not accept any of some of them. So, my opinion is that you should definitely test this flow, instead of trying to set all the permission by default. That just my opinion.

G1 · April 29, 2016, 6:07pm

Is there any other upadate on this permissions issue with Android M. I am stuck with this issue.
@vrunoa could you please provide the above code in Java.
I would really appreciate it.

Thanks

willosser · April 29, 2016, 6:37pm

@vrunoa, I have lots of tests that verify we can add the permissions, that we don’t have expected functionality without the permissions, and that taking those steps without those permissions will cause the app to prompt the user for the necessary permissions. I have far more tests that require all the permissions to be present, and I frequently have to reinstall the app. Adding the permissions each time takes time, and I’d prefer my tests be as quick as possible.

kskrishnan · June 1, 2016, 2:12pm

@willosser, can you please share your java code to read the permission alert text and click on accept / dismiss ?

willosser · June 1, 2016, 2:48pm

I can’t, @kskrishnan, because our code is written in Ruby

Appium gives you an API that detects the activity. Depending upon the device, you could get two different activities - the package name may get stripped off or not:

‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’,
‘.permission.ui.GrantPermissionsActivity’

When you detect this activity, you need to find an element by id:

‘com.android.packageinstaller:id/permission_message’

Then you can obtain the text of that message if you are interested in it. If you care which permission it is, you can match it against expected strings or regular expressions. If not, you can blindly accept by finding and clicking the element by id:

‘com.android.packageinstaller:id/permission_allow_button’

If you’d rather not click ‘allow’ on all those windows, you can use adb to add all the permissions at once before you start testing (but after Appium has installed your app). If you know all the perms your app will need, you can add them with one command:

pm grant $app_name $space_delimited_set_of_perms

Or you can add all perms one at a time, which takes 1.5-2 seconds per attempt.

kskrishnan · June 3, 2016, 5:55am

@willosser - Thanks a ton, works like a charm. However, I wonder it might just be easier if autoAcceptAlerts is made to work in this case. Nevertheless, thanks a lot for your tip - really helped.

Afrin_Sulthana · October 12, 2016, 6:14am

Facing the following issue:
Waiting for pkg: ‘com.sample.testapp’ and activity: ‘com.sample.testapp.MainActivity’ to be focused
2016-10-12 12:11:18:231 - [debug] [ADB] Possible activities, to be checked: com.sample.testapp.MainActivity, .com.sample.testapp.MainActivity

Found package: ‘com.android.packageinstaller’ and activity: ‘.permission.ui.GrantPermissionsActivity’ 2016-10-12 11:27:05:996 - [debug] [ADB] Incorrect package and activity. Retrying.

After Opening an app there is a permission request dialog appearing, i tried to click using the following line of code in java:
driver.findElement(By.id(“com.android.packageinstaller:id/permission_allow_button”)).click();

This is not working. Getting the same error on the appium server as the correct package is not found. can any one suggest me an idea of how to choose the accept button.

Facing this issue in Android N and in Marshmallow.

Aleksei · October 12, 2016, 7:47am

our client asking permissions on start. how we do it.

Start driver with:

Android 6.0:

capabilities.setCapability(“appWaitPackage”, “com.android.packageinstaller”);
capabilities.setCapability(“appWaitActivity”, “.permission.ui.GrantPermissionsActivity”);

Android 7.0:

capabilities.setCapability(“appWaitPackage”, “com.google.android.packageinstaller”);
capabilities.setCapability(“appWaitActivity”, “com.android.packageinstaller.permission.ui.GrantPermissionsActivity”);

Buttons in dialog have ids:

“permission_deny_button”
“permission_allow_button”

use:

driver.findElement(MobileBy.id(“permission_allow_button”)).click();

Afrin_Sulthana · October 12, 2016, 8:04am

DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(“platformName”, “Android”);
capabilities.setCapability(CapabilityType.VERSION, “7.0”);
capabilities.setCapability(“newCommandTimeout”, 1800);
capabilities.setCapability(“appWaitPackage”, “com.google.android.packageinstaller”);
capabilities.setCapability(“appWaitActivity”, “com.android.packageinstaller.permission.ui.GrantPermissionsActivity”);
// capabilities.setCapability(“appWaitDuration”, 4000);
capabilities.setCapability(“autoAcceptAlerts”, true);
capabilities.setCapability(“deviceName”, “Android 7.0”);
capabilities.setCapability(“app”, app.getAbsolutePath());

AndriodDriver
driver = new AndroidDriver(address, getDesiredCapabilities(app));
driver.manage().timeouts().implicitlyWait(80, TimeUnit.SECONDS);
driver.findElement(MobileBy.id(“permission_allow_button”)).click();

This is my code.

But still getting the same error.

2016-10-12 13:28:03:442 - [debug] [UiAutomator] Starting UIAutomator
2016-10-12 13:28:03:443 - [debug] [ADB] Creating ADB subprocess with args: -P, 5037, -s, 00d7c559893a2190, shell, uiautomator, runtest, AppiumBootstrap.jar, -c, io.appium.android.bootstrap.Bootstrap, -e, pkg, com.bits42.admob, -e, disableAndroidWatchers, false, -e, acceptSslCerts, false
2016-10-12 13:28:04:431 - [debug] [UiAutomator] Moving to state ‘online’
2016-10-12 13:28:04:437 - [AndroidBootstrap] [BOOTSTRAP LOG] [debug] json loading complete.
2016-10-12 13:28:04:439 - [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
2016-10-12 13:28:04:443 - [AndroidBootstrap] Android bootstrap socket is now connected
2016-10-12 13:28:04:451 - [debug] [ADB] Device API level: 24
2016-10-12 13:28:04:452 - [debug] [ADB] Getting connected devices…
2016-10-12 13:28:04:459 - [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
2016-10-12 13:28:04:461 - [debug] [ADB] 2 device(s) connected
2016-10-12 13:28:04:462 - [debug] [ADB] Running ‘/home/afrin/Android/Sdk/platform-tools/adb’ with args: ["-P",5037,"-s",“00d7c559893a2190”,“shell”,“am”,“start”,"-W","-n","'com.sample.testapp/'com.sample.testapp.MainActivity","-S","-a",“android.intent.action.MAIN”,"-c",“android.intent.category.LAUNCHER”,"-f",“0x10200000”]
2016-10-12 13:28:06:218 - [debug] [ADB] Waiting for pkg: ‘com.google.android.packageinstaller’ and activity: ‘com.android.packageinstaller.permission.ui.GrantPermissionsActivity’ to be focused
2016-10-12 13:28:06:221 - [debug] [ADB] Possible activities, to be checked: com.android.packageinstaller.permission.ui.GrantPermissionsActivity, .com.android.packageinstaller.permission.ui.GrantPermissionsActivity
2016-10-12 13:28:06:225 - [debug] [ADB] Getting focused package and activity
2016-10-12 13:28:06:227 - [debug] [ADB] Getting connected devices…
2016-10-12 13:28:06:236 - [debug] [ADB] 2 device(s) connected
2016-10-12 13:28:06:237 - [debug] [ADB] Running ‘/home/afrin/Android/Sdk/platform-tools/adb’ with args: ["-P",5037,"-s",“00d7c559893a2190”,“shell”,“dumpsys”,“window”,“windows”]
2016-10-12 13:28:06:293 - [debug] [ADB] Found package: ‘com.android.packageinstaller’ and activity: ‘.permission.ui.GrantPermissionsActivity’
2016-10-12 13:28:06:294 - [debug] [ADB] Incorrect package and activity. Retrying.
2016-10-12 13:28:07:047 - [debug] [ADB] Getting focused package and activity
2016-10-12 13:28:07:049 - [debug] [ADB] Getting connected devices…
2016-10-12 13:28:07:066 - [debug] [ADB] 2 device(s) connected
2016-10-12 13:28:07:067 - [debug] [ADB] Running ‘/home/afrin/Android/Sdk/platform-tools/adb’ with args: ["-P",5037,"-s",“00d7c559893a2190”,“shell”,“dumpsys”,“window”,“windows”]

Aleksei · October 12, 2016, 8:24am

you have android 6.0

Afrin_Sulthana · October 12, 2016, 8:33am

No i am currently running this test in Android 7.0 Android device.

Aleksei · October 12, 2016, 8:34am

no matter then try what i wrote for Android 6.0 capabilities.

Afrin_Sulthana · October 12, 2016, 8:38am

yea tried changing the capability settings as per Android 6.0 also. But getting the same error.

Aleksei · October 12, 2016, 8:39am

you have 2 device connected. may you remove 1 and try both again?

Afrin_Sulthana · October 12, 2016, 8:44am

Still no luck after connecting with a single device.

TmszNL · October 27, 2016, 10:24am

We’ve added a simple while loop in our framework to the method that looks up elements:

while(autoAcceptPerms && _driver.currentActivity().contains(“GrantPermissionsActivity”)){
_driver.findElement(By.id(“com.android.packageinstaller:id/permission_allow_button”)).click();
}

The autoAcceptPerms boolean is configurable by constructor. This results in permission dialogs to be immediately accepted when they appear.

JorgeV · October 27, 2016, 9:03pm

I think it is simpler if you grant the permissions with adb before starting the app.

subprocess.Popen("adb shell pm grant <package name> android.permission.ACCESS_FINE_LOCATION", shell=True).communicate()

Aleksei · January 6, 2017, 3:53pm

with latest 1.6.3 Appium use:

capabilities.setCapability(“autoGrantPermissions”, “true”);

cavanpage · January 6, 2017, 9:01pm

@Aleksei

I am using appium 1.6.3 on Android M and using …

capabilities.setCapability(“autoGrantPermissions”, “true”);

I’m launching chrome but the permission pop ups are still occurring.