Neither user 10102 nor current process has android.permission.READ_PHONE_STATE

Question

I am trying to call getCallCapablePhoneAccounts() method of android.telecom.TelecomManager class. Though i have added required user-permission, i am getting Security exception.

Here is the line of code where i am getting exception

List<PhoneAccountHandle> list = getTelecomManager().getCallCapablePhoneAccounts();

user permission added in manifest

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

Exception stacktrace Caused by: java.lang.SecurityException: getDefaultOutgoingPhoneAccount: Neither user 10102 nor current process has android.permission.READ_PHONE_STATE. at android.os.Parcel.readException(Parcel.java:1599) at android.os.Parcel.readException(Parcel.java:1552) at com.android.internal.telecom.ITelecomService$Stub$Proxy.getDefaultOutgoingPhoneAccount(ITelecomService.java:615) at android.telecom.TelecomManager.getDefaultOutgoingPhoneAccount(TelecomManager.java:439)

Try a clean and rebuild. If not, deleting the permission and re-adding it supposedly fixes things: http://stackoverflow.com/questions/12778168/access-network-state-permisson-on-android-ics/12778460#12778460 — Chris Stillwell, Sep 23 '15 at 14:32
I am also getting the same issue, after I upgraded my emulator target android 6. @Prasad were you able to find a solution? — Rusheel Jain, Sep 24 '15 at 04:24
It seems this is some issue with Android M https://code.google.com/p/android-developer-preview/issues/detail?id=2938 — Rusheel Jain, Sep 24 '15 at 04:29
@Rusheel, not yet found the solution. These APIs are added in level 23(android M). It seems to be a bug in the framework — Prasad, Sep 24 '15 at 05:40
@Prasad You can try to compile your app for api 23 i.e. compile sdk version 23 and target sdk version 23. While on the emulator you can run an older Android like Lollipop (API 21). This should work. I know this is just a workaround to check if your code works fine till a solution for permissions issue is released by android developers — Rusheel Jain, Sep 24 '15 at 07:00

score 84 · Answer 1 · edited Sep 24 '18 at 12:17

84

On Android >=6.0, We have to request permission runtime.

Step1: add in AndroidManifest.xml file

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

Step2: Request permission.

int permissionCheck = ContextCompat.checkSelfPermission(this, Manifest.permission.READ_PHONE_STATE);

if (permissionCheck != PackageManager.PERMISSION_GRANTED) {
    ActivityCompat.requestPermissions(this, new String[]{Manifest.permission.READ_PHONE_STATE}, REQUEST_READ_PHONE_STATE);
} else {
    //TODO
}

Step3: Handle callback when you request permission.

@Override
public void onRequestPermissionsResult(int requestCode, String permissions[], int[] grantResults) {
    switch (requestCode) {
        case REQUEST_READ_PHONE_STATE:
            if ((grantResults.length > 0) && (grantResults[0] == PackageManager.PERMISSION_GRANTED)) {
                //TODO
            }
            break;

        default:
            break;
    }
}

Edit: Read official guide here Requesting Permissions at Run Time

edited Sep 24 '18 at 12:17

Morteza Jalambadani

2,016
6
21
33

answered Aug 05 '16 at 06:48

sonnv1368

1,507
11
17

6

Thank for this. Don't forget, you also need to ensure your activity `implements ActivityCompat.OnRequestPermissionsResultCallback`. – ban-geoengineering Sep 06 '16 at 13:11
@ban-geoengineering: Thanks – sonnv1368 Sep 07 '16 at 03:41
3

the right package is android.Manifest.permission.READ_PHONE_STATE – SalmanShariati Dec 17 '16 at 20:36
I got this error on Xiaomi Mi 4i **os version:5.0.2** so what can i do? – Bhavin Patel Mar 28 '17 at 12:07
REQUEST_READ_PHONE_STATE here is an app-defined int constant. The callback method gets the result of the request (comment from documentation). – LLAlive Nov 16 '17 at 11:04
1

I get **Cannot resolve symbol REQUEST_READ_PHONE_STATE** – phrogg Jan 10 '19 at 19:24
4

Got it, I forgot this `private final int REQUEST_READ_PHONE_STATE=1;` – phrogg Jan 10 '19 at 19:27

score 54 · Answer 2 · answered Nov 27 '15 at 07:09

54

Are you running Android M? If so, this is because it's not enough to declare permissions in the manifest. For some permissions, you have to explicitly ask user in the runtime: http://developer.android.com/training/permissions/requesting.html

answered Nov 27 '15 at 07:09

LVR

714
5
6

2

This is one possible solution, I don't understand why it is downvoted. – Vedavyas Bhat Dec 30 '15 at 07:40
1

Yeah you are right. On android M this is the solution +1 :) – Mohammad Jan 03 '16 at 08:58
3

Wrong answer! I am running Android M, but targeting Android L. In such case it IS enough to declare permissions in the manifest. Correct answer to the question is to declare permission `android.Manifest.permission.READ_PHONE_STATE` instead of `android.permission.READ_PHONE_STATE`. – zyamys Apr 26 '17 at 16:56
3

@zyamys that is not enough: if you target Android L the permission is automatically granted at installation time, but the user can always disable it from system settings. – manfcas May 24 '17 at 11:02

score 10 · Answer 3 · answered May 23 '17 at 15:10

10

I was experiencing this problem on Samsung devices (fine on others). like zyamys suggested in his/her comment, I added the manifest.permission line but in addition to rather than instead of the original line, so:

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

I'm targeting API 22, so don't need to explicitly ask for permissions.

answered May 23 '17 at 15:10

mrrrk

1,995
18
15

I'm experiencing a very similar issue mainly with Samsung devices. Did you find a solution? – Mattia Campana Mar 28 '18 at 15:28

Neither user 10102 nor current process has android.permission.READ_PHONE_STATE

3 Answers3

Linked