ActivityCompat requestPermissions not showing dialog box

Question

if  ContextCompat checkSelfPermission RegisterActivity this       Manifest permission READ PHONE STATE     PackageManager PERMISSION DENIED               ActivityCompat requestPermissions this                      new String   Manifest permission READ PHONE STATE   REQUEST READ PHONE STATE PERMISSION     i m trying to use this function on nexus 5 api 23 and its just not showing me the dialog box like its supposed to do  it s just not doing anything  what could cause the problem   this code is in the java activity  i tried changing my minimum api to 23 and use the requestPermissions   without the ActivityCompat but still not working   apply plugin   com android application   android   compileSdkVersion 23 buildToolsVersion  23 0 2   defaultConfig       applicationId  com example idanayzen photomap      minSdkVersion 23     targetSdkVersion 23     versionCode 1     versionName  1 0    buildTypes       release           minifyEnabled false         proguardFiles getDefaultProguardFile  proguard-android txt     proguard-rules pro             dependencies   compile fileTree dir   libs   include      jar    testCompile  junit junit 4 12  compile  com android support appcompat-v7 23 1 1  compile  com google android gms play-services 8 4 0  compile  com android support design 23 1 1      and the Manifest    lt  xml version  1 0  encoding  utf-8   gt   lt manifest xmlns android  http   schemas android com apk res android  package  com example idanayzen photomap  gt    lt uses-permission android name  android permission ACCESS FINE LOCATION    gt   lt uses-permission android name  android permission READ PHONE STATE    gt   lt uses-permission android name  android permission READ SMS    gt    lt application     android allowBackup  true      android icon   mipmap ic launcher      android label   string app name      android supportsRtl  true      android theme   style AppTheme  gt         lt meta-data         android name  com google android geo API KEY          android value   string google maps key    gt        lt activity         android name   MapsActivity          android label   string title activity maps    gt       lt activity android name   RegisterActivity  gt           lt intent-filter gt               lt action android name  android intent action MAIN    gt                lt category android name  android intent category LAUNCHER    gt           lt  intent-filter gt       lt  activity gt       lt activity android name   WrongPhoneNum  gt  lt  activity gt   lt  application gt    lt  manifest gt

User · Answer

I had a need to request permission for WRITE EXTERNAL STORAGE but was not getting a pop-up despite trying all of the different suggestions mentioned   The culprit in the end was HockeyApp  It uses manifest merging to include its own permission for WRITE EXTERNAL STORAGE except it applies a max sdk version onto it   The way to get around this problem is to include it in your Manifest file but with a replace against it  to override the HockeyApp s version and success      4 7 2 Other dependencies requesting the external storage permission  SDK version 5 0 0 and later  To be ready for Android O    HockeySDK-Android 5 0 0 and later limit the WRITE EXTERNAL STORAGE   permission with the maxSdkVersion filter  In some use cases  e g    where an app contains a dependency that requires this permission    maxSdkVersion makes it impossible for those dependencies to grant or   request the permission  The solution for those cases is as follows     lt uses-permission android name  android permission WRITE EXTERNAL STORAGE  tools node  replace   gt       It will cause that other attributes from low   priority manifests will be replaced instead of being merged    https   support hockeyapp net kb client-integration-android hockeyapp-for-android-sdk permissions-advanced

User · Answer

For me the problem was that right after making the request  my main activity launched another activity  That superseded the dialog so it was never seen

User · Answer

Replace   ActivityCompat requestPermissions this  new String    Manifest permission READ PHONE STATE    225     with   ActivityCompat requestPermissions this  new String   Manifest permission READ PHONE STATE   225     The actual string for that permission is not  Manifest permission READ PHONE STATE   Use the symbol Manifest permission READ PHONE STATE

User · Answer

I was having the same problem  and solved it by replacing Manifest permission READ PHONE STATE with android Manifest permission READ PHONE STATE

User · Answer

I had the same issue and it turned out to be due to the manifest merger tool pulling in an android:maxSdkVersion attribute from a dependency.

To view the actual permissions you're requesting in your APK you can use the aapt tool, like this:

/path/to/android-sdk/build-tools/version/aapt d permissions /path/to/your-apk.apk

in my case, it printed:

uses-permission: name='android.permission.WRITE_EXTERNAL_STORAGE' maxSdkVersion='18'

even though I hadn't specified a maxSdkVersion in my manifest. I fixed this issue by changing <uses-permission> in my manifest to:

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

(where the tools namespace is http://schemas.android.com/tools)

User · Answer

it happen to me i was running it on API 23 and i had to use the code to request permission like this code below put it on on create method. note that MY_PERMISSIONS_REQUEST_READ_LOCATION is an integer that is equal to 1 example int MY_PERMISSIONS_REQUEST_READ_LOCATION = 1:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) { requestPermissions(new String[]{ Manifest.permission.ACCESS_COARSE_LOCATION},MY_PERMISSIONS_REQUEST_READ_LOCATION); }

User · Answer

I updated my target SDK version from 22 to 23 and it worked perfectly

User · Answer

For me the issue was I had an invalid request code  I choose 0xDEADBEEF as a request code and it was silently failing  maybe it s cast to something smaller than 32-bit somewhere internally   If I choose 255 everything worked fine as NightSkyDev described above

User · Answer

No matter what you do  Check if you declare Permission you need in the Manifest file         lt  --Declaring the required permissions-- gt       lt uses-permission         android name  android permission READ EXTERNAL STORAGE    gt       lt uses-permission         android name  android permission WRITE EXTERNAL STORAGE    gt       lt uses-permission         android name  android permission CAMERA    gt      Then go to next steps

User · Answer

It could be not a problem with a single line of your code.

On some devices (I don't recall if it is in stock Android) the Permission dialog includes a check box labeled "Never ask again". If you click Deny with the box checked then you won't be prompted again for that permission, it will automatically be denied to the app. To revert this, you have to go into Settings -> App -> Permissions and re--enable that perm for the app. Then turn it off to deny it again. You may have to open the app before turning it off again, not sure.

I don't know if your Nexus has it. Maybe worth a try.

User · Answer

The above information is good  but setting targetSdkVersion to 23  or higher  is critical for Android to interpret the  lt uses-permission gt  tag in the manifest as  I will ask in code  instead of  I demand upon installation    Lots of sources will tell you that you need the  lt uses-permission gt  tag  but no one says why and if you don t have that value set  you re going to be as confused as I was for hours on end

User · Answer

Maybe this solution could help anyone rather than:

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

use :

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

so we add android. to Manifest.permission.WRITE_EXTERNAL_STORAGE

User · Answer

For me the error was in the manifest  the permission was in uppercase  Android Studio suggest me the permissions in uppercase  I don t care about that and it took me two hours to fixe this problem   The right syntaxe for permission is   lt uses-permission android name  android permission WRITE EXTERNAL STORAGE   gt

User · Answer

I came across this problem in Samsung S8 and N8 (havent found in any other)

so the problem is in the manifest file uses-permission

<uses-permission android:name="android.permission.CAMERA"
android:requiredFeature="true" />

For some reason, the attribute android:requiredFeature is the culprit. and I haven't found the explanation on why.

to solve simply remove it,

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

User · Answer

For me the issue was requesting a group mistakenly instead of the actual permissions

User · Answer

Don t forget to write the permissions without extra spaces in the manifest  In my case i had    lt uses-permission android name  android permission WRITE EXTERNAL STORAGE     gt    But look  at the end  there s an extra space  Just write it the right way    lt uses-permission android name  android permission WRITE EXTERNAL STORAGE    gt    And it s working now

User · Answer

This just happened to me   It turned out I was requesting ALL permissions  when I needed to filter to just DANGEROUS permissions  and it suddenly started working   fun requestPermissions         val missingDangerPermissions   PERMISSIONS              filter   ContextCompat checkSelfPermission this  it     PackageManager PERMISSION GRANTED                filter   this getPackageManager   getPermissionInfo it  PackageManager GET META DATA  protectionLevel    PermissionInfo PROTECTION DANGEROUS      THIS FILTER HERE       if  missingDangerPermissions isNotEmpty              Log i TAG   Requesting dangerous permission to  missingDangerPermissions            ActivityCompat requestPermissions this                  missingDangerPermissions toTypedArray                    REQUEST CODE REQUIRED PERMISSIONS           return       else           Log i TAG   We had all the permissions we needed  yay

User · Answer

I had this same issue I updated to buildToolsVersion  23 0 3  It all of a sudden worked  Hope this helps anyone having this issue

User · Answer

Here is another experience I d like to share with you guys  The problem showed up after I implemented the following code to check for BLE access permission   final String requiredPermission    Build VERSION SDK INT  gt   Build VERSION CODES Q  amp  amp  targetSdkVersion  gt   Build VERSION CODES Q                android Manifest permission ACCESS FINE LOCATION               android Manifest permission ACCESS COARSE LOCATION    I meant to distinguish between FINE and COARSE location permission requests  both had been defined in the manifest  When checking for ACCESS COARSE LOCATION permission  the  Request permission  dialog never poped up but onRequestPermissionsResult was always called with PERMISSION DENIED  in case permission was not enabled in app settings   So I removed the check for BUILD SDK and checked only for ACCESS FINE LOCATION and voilla the missing dialog showed up   final String requiredPermission   android Manifest permission ACCESS FINE LOCATION    did the trick   The Manifest source contains    lt uses-permission android name  android permission COARSE LOCATION    gt   lt uses-permission android name  android permission ACCESS FINE LOCATION    gt    but the apk contained android permission ACCESS FINE LOCATION only  Sometime during build  the COARSE LOCATION had been removed   I hope this might help somebody having the same issue

User · Answer

Here s an example of using requestPermissions     First  define the permission  as you did in your post  in the manifest  otherwise  your request will automatically be denied    lt uses-permission android name  android permission READ PHONE STATE    gt    Next  define a value to handle the permission callback  in onRequestPermissionsResult       private final int REQUEST PERMISSION PHONE STATE 1    Here s the code to call requestPermissions     private void showPhoneStatePermission         int permissionCheck   ContextCompat checkSelfPermission              this  Manifest permission READ PHONE STATE       if  permissionCheck    PackageManager PERMISSION GRANTED            if  ActivityCompat shouldShowRequestPermissionRationale this                  Manifest permission READ PHONE STATE                 showExplanation  Permission Needed    Rationale   Manifest permission READ PHONE STATE  REQUEST PERMISSION PHONE STATE             else               requestPermission Manifest permission READ PHONE STATE  REQUEST PERMISSION PHONE STATE                   else           Toast makeText MainActivity this   Permission  already  Granted    Toast LENGTH SHORT  show              First  you check if you already have permission  remember  even after being granted permission  the user can later revoke the permission in the App Settings      And finally  this is how you check if you received permission or not    Override public void onRequestPermissionsResult          int requestCode          String permissions            int   grantResults        switch  requestCode            case REQUEST PERMISSION PHONE STATE              if  grantResults length  gt  0                      amp  amp  grantResults 0     PackageManager PERMISSION GRANTED                    Toast makeText MainActivity this   Permission Granted    Toast LENGTH SHORT  show                  else                   Toast makeText MainActivity this   Permission Denied    Toast LENGTH SHORT  show                           private void showExplanation String title                               String message                               final String permission                               final int permissionRequestCode        AlertDialog Builder builder   new AlertDialog Builder this       builder setTitle title               setMessage message               setPositiveButton android R string ok  new DialogInterface OnClickListener                     public void onClick DialogInterface dialog  int id                        requestPermission permission  permissionRequestCode                                         builder create   show       private void requestPermission String permissionName  int permissionRequestCode        ActivityCompat requestPermissions this              new String   permissionName   permissionRequestCode

[java] ActivityCompat.requestPermissions not showing dialog box

The answer is

No matter what you do, Check if you declare Permission you need in the Manifest file.

Examples related to java

Examples related to android

Examples related to permissions

Tags