Android M permission dialog not showing

Question

I'm currently trying to adapt my application to the new permissions model of Android M.

I'm collecting all the permissions I require, then run

Log.i("Permissions", "Requesting permissions: " + permissions);
requestPermissions(requiredPermissions.toArray(new String[requiredPermissions.size()]), requestCodeForPermissions);

requiredPermissions holds the permissions I need like android.permission.WRITE_EXTERNAL_STORAGE.

That routine is definitely executed as I have the Log line in the logcat:

08-07 12:52:46.469: I/Permissions(1674): Requesting permissions: android.permission.RECEIVE_BOOT_COMPLETED; android.permission.WRITE_EXTERNAL_STORAGE

But the permissions dialog never shows, let alone is onRequestPermissionsResult() called.

What am I doing wrong? Based on some tutorials I found I'm not missing anything. I only have the emulator for testing, no physical device. This is the about screen from settings: Image

It might be worth mentioning something else: If I try to open the overview of installed apps from the home screen I only get launcher3 has exited. I'm not sure if that might be related.

Does anybody have an idea why it's not showing?

What version of the M Developer Preview are you using? In v1, `WRITE_EXTERNAL_STORAGE` was not `dangerous` and did not need to be requested manually. That changed in v2, where it works like other `dangerous` permissions like `CAMERA`. Note that `RECEIVE_BOOT_COMPLETED` is not a `dangerous` permission; you do not have to request it at runtime. — CommonsWare, Aug 07 '15 at 13:08
I have v2. For the sake of testing I added record audio which is now requested: 08-07 13:49:31.647: I/Permissions(1540): Requesting permissions: android.permission.RECEIVE_BOOT_COMPLETED; android.permission.WRITE_EXTERNAL_STORAGE; android.permission.RECORD_AUDIO This is from my manifest: And this is from the project.properties file: target=android-MNC targetSdkVersion=MNC compileSdkVersion=android-MNC Am I missing anything that might be obvious for others? — Jens, Aug 07 '15 at 13:50
Do you have the `` elements in your manifest? The new runtime permissions model does not eliminate the need for `` elements. It just adds additional requirements for requesting permissions at runtime for select permission groups. — CommonsWare, Aug 07 '15 at 13:52
Yes, my manifest still contains all the old uses-permission elements. — Jens, Aug 07 '15 at 13:54
Well, [this sample app of mine](https://github.com/commonsguy/cw-omnibus/tree/master/Permissions/PermissionMonger) seems to work fine on MNC v2. Compare and contrast what you have with what I have. — CommonsWare, Aug 07 '15 at 14:04
Thanks for that. Well, I don't currently use Android Studio, but still Eclipse. Most tutorials about this mention the build.gradle file for some lines. Could it be Android Studio is a requirement for the permission model? The actual source code seems identical. — Jens, Aug 07 '15 at 23:54
"Could it be Android Studio is a requirement for the permission model?" -- it's conceivable, at least for the preview. Eclipse might work better once M ships and we have a regular API level number to work with. That being said, since Google is abandoning support for Eclipse at the end of the year, I really encourage you to have a plan for issues like this one, as there will come a time when you literally cannot build what you want using Eclipse+ADT. With luck, Andmore will be able to fill the gap by then. — CommonsWare, Aug 08 '15 at 10:21
in my case i had set a maxsdk for the WRITE permission, because i wasn't ready to deal with permissions(earlier), so i just targeted API 21. so all i had to do was remove the MAXSDK restriction and it worked. — Peterstev Uremgba, Oct 22 '17 at 16:16

score 124 · Answer 1 · answered Nov 29 '15 at 09:25

124

I experienced the same issue but later I realized I forgot to add the permission to the manifest file. After adding the uses-permission tag, the system showed the dialog. Maybe helps someone.

answered Nov 29 '15 at 09:25

Tamás Cseh

3,050
1
20
30

13

pfff.wasted almost 2 hours until this post (in manifest was coarse_location in code fine_location).... – Alexandru Circus Mar 21 '16 at 23:01
Same here... Thanks ! – Silas Jun 02 '16 at 22:44
3

Awesome! That's the problem when developing fast! You miss basic things behind. Thanks! – Guillem Roca Aug 05 '16 at 10:46
Interesting, me either=)) – Hilal Aug 06 '16 at 08:22
2

But it did not fixed because I also used tabhost and that is probably also problem when you want to show permissin dialog, [found this post](http://stackoverflow.com/a/37142595/5528870) – Hilal Aug 06 '16 at 08:51
Make sure everything is spelled right, too. I had `android.permissoin.WRITE_EXTERNAL_STORAGE` – Jon McClung Dec 18 '16 at 07:33
Do make sure that the capitalization is the same. Android will happily case-convert when it checks the permission on install, but it does not do so when comparing the requested permission with your manifest. – AI0867 Aug 09 '17 at 14:15
Good to know about this. – sam_k Oct 19 '17 at 02:02

score 32 · Answer 2 · edited Jan 10 '23 at 00:11

32

The original answer helped me.

I fixed by adding tools:remove="android:maxSdkVersion" like this:

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" tools:remove="android:maxSdkVersion"/>

edited Jan 10 '23 at 00:11

Willi Mentzel

27,862
20
113
121

answered Sep 18 '17 at 05:29

Khang .NT

1,504
6
24
46

This solved my issue with having the permissions denied at runtime. – Joules Dec 29 '20 at 14:17

score 14 · Answer 3 · answered Dec 23 '15 at 10:16

14

I experienced the same issue because I was using the negative value as a REQUEST_CODE.

requestPermissions(new String[]{android.Manifest.permission.CAMERA}, -1)

After using positive value, the system showed the dialog. Hope it helps someone.

answered Dec 23 '15 at 10:16

shanraisshan

3,521
2
21
44

This was the solution. Absolutely bizarre that negative numbers cause Android to fail in such a subtle and infuriating way. – aroth Dec 02 '16 at 05:26
Thanks!, this was my case as I didn't want to attend the callback – jevora Jan 16 '17 at 13:12
You saved my life – YON Oct 28 '17 at 15:42

score 10 · Accepted Answer · answered Feb 13 '17 at 17:16

10

Based on the comment from Hilal (thanks a lot!): In my case my app is indeed using tabhost and the permissions were requested from an Activity inside the tabhost. After starting a separate activity that requests the permissions it is working.

answered Feb 13 '17 at 17:16

Jens

1,157
1
8
17

score 9 · Answer 5 · edited Sep 24 '16 at 13:38

9

add

 <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

in AndroidManifest.xml

Note : The Permission which you want to get. Eg: android.permission.ACCESS_FINE_LOCATION etc.

edited Sep 24 '16 at 13:38

Pravinraj Venkatachalam

294
5
13

answered Feb 03 '16 at 06:21

Vinil Chandran

1,563
1
19
33

This was my issue. Don't get fooled by the official doc telling you to set a maxSdk value. :( – althaus Apr 04 '16 at 10:30

score 9 · Answer 6 · answered Mar 30 '16 at 14:08

I just had the same problem. My issue was that I wrote the permission at the wrong place in the manifest. Make sure the uses permission is outside of application:

    <?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.google.android.gms.samples.vision.face.photo"
    android:installLocation="auto"
    android:versionCode="1"
    android:versionName="1" >

    <uses-sdk
        android:minSdkVersion="9"
        android:targetSdkVersion="21" />

    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>


    <application
        android:hardwareAccelerated="true"
        android:label="FacePhotoDemo"
        android:allowBackup="true"
        android:icon="@drawable/icon">

score 2 · Answer 7 · answered Oct 14 '15 at 16:00

I have also come across a situation where the permission dialog doesn't appear or the application crashes when using the <uses-permission-sdk23> element, however the cause appears to be a system bug on current 6.0 devices:

https://code.google.com/p/android/issues/detail?id=189841

Crash exception:

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity}: java.lang.NullPointerException: Attempt to get length of null array

score 2 · Answer 8 · answered Feb 26 '16 at 09:14

2

I have the same issue and the problem is solved after adding the shouldShowRequestPermissionRationale like this:

if (ActivityCompat.shouldShowRequestPermissionRationale(thisActivity,
        Manifest.permission.READ_CONTACTS)) {

} else {
    ActivityCompat.requestPermissions(thisActivity,
            new String[]{Manifest.permission.READ_CONTACTS},
            MY_PERMISSIONS_REQUEST_READ_CONTACTS);

}

answered Feb 26 '16 at 09:14

Hai nguyen thanh

718
7
17

2

This wouldn't change anything – Chad Bingham Sep 15 '16 at 02:18

score 2 · Answer 9 · answered Dec 07 '16 at 13:22

2

To add to @shanraisshan's answer, the REQUEST_CODE actually has to be greater than 0, not just non-negative.

answered Dec 07 '16 at 13:22

joakim

3,533
2
23
28

score 2 · Answer 10 · edited Apr 07 '17 at 02:48

2

In our code, it was a simple spelling mistake.

We had:

<uses-permission android:name="android.permission.ACCESS_COURSE_LOCATION" />

It should be:

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

edited Apr 07 '17 at 02:48

Pang

9,564
146
81
122

answered Apr 07 '17 at 02:27

RJ.

141
1
4

paperduck · Answer 11 · 2017-09-06T10:16:14.563

2

I was doing two calls to requestPermissions(), one right after the other. This error message appeared in Logcat (note the misspelling on "request"):

Can reqeust only one set of permissions at a time

requestPermissions() is actually designed to take multiple requests at once; that's what the String array is for.

edited Sep 06 '17 at 10:16

answered Sep 06 '17 at 10:11

paperduck

1,175
1
16
26

score 2 · Answer 12 · answered Jan 26 '18 at 07:06

2

In my case, the permission I was requesting (WRITE_SETTINGS) was more special and required Settings Activity to launch. So dialog was not showing up.

I had to get its permission using the following code:

Intent intent = new Intent(Settings.ACTION_MANAGE_WRITE_SETTINGS);
intent.setData(Uri.parse("package:" + context.getPackageName()));
startActivityForResult(intent, CODE_WRITE_SETTINGS_PERMISSION);

answered Jan 26 '18 at 07:06

M. Usman Khan

3,689
1
59
69

`WRITE_SETTINGS` is treated as a _special permission_ and requires special handling: https://developer.android.com/guide/topics/permissions/overview#special_permissions – ccpizza Feb 03 '19 at 22:31

score 2 · Answer 13 · answered Sep 22 '18 at 19:24

2

Yet another cause for not getting the permission dialog to show when requesting a dangerous permission...

I had to do Build -> Clean Project and then Build -> Rebuild Project. I guess Android Studio didn't pick up on the changes I made in the manifest.

answered Sep 22 '18 at 19:24

Magnus

17,157
19
104
189

I wasted half a day to figure out what's wrong with my code. Thanks a lot :) – hidd Jun 28 '19 at 19:48

score 2 · Answer 14 · answered Mar 30 '19 at 11:04

I had a similar issue caused by the wrong case of the permission constant in the manifest, I was using read_contacts in lower case:

<uses-permission android:name="android.permission.read_contacts" />

After changing read_contacts to uppercase it started working as expected

<uses-permission android:name="android.permission.READ_CONTACTS" />

score 1 · Answer 15 · answered Mar 05 '16 at 23:40

Permissions are organised into categories so non-critical ones are granted without the dialog being shown.

I found this the hard way with internet permission, if you're having this issue then changing to a critical permission such as read_contacts will allow you to test your flow and reveal whether the issue is the permission being non-critical or something else.

Normal protection permissions are listed here

score 1 · Answer 16 · answered Aug 25 '16 at 19:17

1

In the manifest, I changed

 <uses-permission
    android:name="android.permission.WRITE_EXTERNAL_STORAGE"
    android:maxSdkVersion="22" />

to

 <uses-permission
    android:name="android.permission.WRITE_EXTERNAL_STORAGE"
     />

Maybe that helps.

answered Aug 25 '16 at 19:17

mogile_oli

2,148
2
21
21

score 1 · Answer 17 · answered Oct 13 '16 at 07:25

1

Add permission in the manifest file as well.

answered Oct 13 '16 at 07:25

Phani varma

475
5
7

score 1 · Answer 18 · answered Jul 19 '17 at 04:56

If anyone of you guys has an application that changes/modifies WRITE_SETTINGS and are facing this issue. Check out CommonsWare's Answer to WRITE_SETTINGS Ambiguity

I was facing this issue for 2 weeks and later realised that this issue was due to the fact that requestPermissions doesn't work for requesting WRITE_SETTINGS permission. Hope this helps :D

score 1 · Answer 19 · answered Aug 28 '17 at 08:04

1

In my case I had requested "ACCESS_COARSE_LOCATION" in my manifest file and then request for "ACCESS_FINE_LOCATION" permission in code that's why the Permission Dialog was not opening.

answered Aug 28 '17 at 08:04

Akash Bisariya

3,855
2
30
42

score 0 · Answer 20 · answered Aug 18 '15 at 13:34

0

After searching a while it appears it is required to set the value compileSdkVersion to "android-MNC" or as of today to 23. That requires the Gradle build system which then seems to require Android Studio. At least I couldn't find a single manual about how to set it outside the gradle files.

answered Aug 18 '15 at 13:34

Jens

1,157
1
8
17

I have the same issue and haven't managed to solve it yet. Reading your answer does not really help me solve it? Could you please clarify a bit more? My compileSdkVersion was and still is 23 and I still get this error. – SudoPlz Nov 19 '15 at 14:16
me too. Your answer worth nothing, because below 23 there was no Runtime Permissions. – Evgeniy Mishustin Jan 08 '16 at 14:26
Why is it worth nothing? I merely said it doesn't seem to work to achieve this if one is using Eclipse. – Jens Jan 09 '16 at 23:21

score 0 · Answer 21 · answered Feb 15 '16 at 12:54

0

I did all the things said in above answers but still dialog was not showing and then I changed targetSdkVersion to 23 in gradle and it appeared . Hope this helps someone

answered Feb 15 '16 at 12:54

Naveen Rao

712
6
10

Ahmad Aghazadeh · Answer 22 · 2016-04-30T14:42:36.877

@Override
    public final void validateRequestPermissionsRequestCode(int requestCode) {
       // We use 16 bits of the request code to encode the fragment id when
       // requesting permissions from a fragment. Hence, requestPermissions()
       // should validate the code against that but we cannot override it as we
       // can not then call super and also the ActivityCompat would call back to
       // this override. To handle this we use dependency inversion where we are
       // the validator of request codes when requesting permissions in
       // ActivityCompat.
        if (!mRequestedPermissionsFromFragment
                && requestCode != -1 && (requestCode & 0xffff0000) != 0) {
            throw new IllegalArgumentException("Can only use lower 16 bits for requestCode");
        }
    }

score 0 · Answer 23 · answered Aug 18 '16 at 04:58

Had the same issue. Later I realized that we have to declare each and every permission in manifest (even if one is a subclass of another). In my case I declared

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

in my manifest and was trying to access user's coarse location.

ContextCompat.checkSelfPermission(this, Manifest.permission.ACCESS_COARSE_LOCATION)

Fixed the problem by adding coarse permission as well in manifest.

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>

score 0 · Answer 24 · answered Dec 19 '16 at 22:02

0

Set your targetSdkVersion to 22.

answered Dec 19 '16 at 22:02

Iman Marashi

5,593
38
51

score 0 · Answer 25 · answered Jan 17 '17 at 08:41

0

had the same (i guess) problem and the solution was removing

import <app package>.Manifest;

autoimported by Android Studio at the top of the file and substitute it with

import android.Manifest;

and started working

answered Jan 17 '17 at 08:41

Alberto Cappellina

328
5
18

score 0 · Answer 26 · answered Jan 18 '17 at 20:10

0

In my case the solution is the string itself

android.permission.READ_CONTACTS

I did Manifest.permission.READ_CONTACTS which caused silence error (Noting show on the screen).

Make sure that this is correct

answered Jan 18 '17 at 20:10

Kadir Erturk

583
6
8

Manifest.permission.READ_CONTACTS = "android.permission.READ_CONTACTS" – M. Usman Khan Jan 26 '18 at 04:03

score 0 · Answer 27 · answered Jan 29 '20 at 00:29

My Android targetSDK version is 28.

I don't see any pop ups shown to user requesting for permission which are listed in android Manifest.xml as . During both installation, installing .apk using USB and installing app from google play store. So I added below code in my activity it will ask user permission during runtime

ActivityCompat.requestPermissions(MyActivity.this, new String[]{Manifest.permission.READ_PHONE_STATE}, 1);

score 0 · Answer 28 · answered Jun 26 '20 at 10:07

0

I was requesting permission through code, but had missed adding the <uses-permission ..> tag in manifest !

answered Jun 26 '20 at 10:07

AndroidGuy

1,270
4
15
32

score -1 · Answer 29 · answered Sep 08 '17 at 18:34

-1

Change the final constant value to 1.

private static final int REQUEST_PERMISSION_WRITE = 1;

ActivityCompat.requestPermissions(this,new String[]{Manifest.permission.WRITE_EXTERNAL_STORAGE},REQUEST_PERMISSION_WRITE);

answered Sep 08 '17 at 18:34

anto004

287
2
6

Android M permission dialog not showing

29 Answers29

Linked