missing permissions required by BluetoothAdapter.isEnabled.BLUETOOTH

Question

I add bluetooth to my app but am running into the following problem. When I do the code:

BluetoothAdapter bluetoothAdapter=BluetoothAdapter.getDefaultAdapter();
if (bluetoothAdapter == null) {
    Toast.makeText(getApplicationContext(),"Device doesnt Support Bluetooth",Toast.LENGTH_SHORT).show();
}

if(!bluetoothAdapter.isEnabled()) {
    Intent enableAdapter = new Intent(BluetoothAdapter.ACTION_REQUEST_ENABLE);
    startActivityForResult(enableAdapter, 0);
}

The error is on the following line:

if(!bluetoothAdapter.isEnabled())

Error:

Missing permissions required by BluetoothAdapter.isEnabled :android.permissions.BLUETOOTH

I added the following permissions to the android manifest file:

<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
<permission android:name="android.permission.BLUETOOTH" android:label="BLUETOOTH" />
<permission android:name="android.permission.BLUETOOTH_ADMIN" />

but am still getting the same issue. Do you know what I did wrong?

Are you testing with Android 6.0 or above? You need to request permission at the run time. Having permission in the `AndroidManifest.xml` is not enough. Read here: https://developer.android.com/training/permissions/requesting.html See a simple example here: http://stackoverflow.com/questions/33666071/android-marshmallow-request-permission?answertab=active#tab-top — ᴛʜᴇᴘᴀᴛᴇʟ, Oct 22 '16 at 23:44
@th3pat3l could you tell me specifically how to do run time permissions for bluetooth? — ComputerGeek101, Oct 23 '16 at 00:08
@ComputerGeek101 check out my answer. It should give you an idea on what you have to do in Android M and above — ᴛʜᴇᴘᴀᴛᴇʟ, Oct 23 '16 at 00:32
When I type @RequiredApi it gives me an error. Do you know why? It says cannot resolve symbol. — ComputerGeek101, Oct 23 '16 at 22:46

score 4 · Answer 1 · answered Oct 23 '16 at 00:31

Let's say you have a button and then you click on it, Bluetooth needs to turn on. Here's a quick example how you would do it for Android 6.0 and above.

First, declare this variable in your Activity/Fragment:

public static final int PERMISSION_ASK = 1001;

Now, let's say this buttons is going to enable the bluetooth. setOnClickListener:

myButton.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View view) {
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
            if(isBluetoothPermissionGranted()) {
                // app already has required permissions
                // do some task here
            } else {
                // app does not have permission yet.
                // ask for permissions
                askForBluetoothPermissions();
            }
        } else {
            // Android version below 6.0, no need to check or ask for permission
            // do some task here
        }
    }
});

Checking if application already has the required permission:

@RequiresApi(api = Build.VERSION_CODES.M)
private boolean isBluetoothPermissionGranted() {
    boolean granted = false;
    int bluetoothGranted = checkSelfPermission(Manifest.permission.BLUETOOTH);
    int bluetoothAdminGranted = checkSelfPermission(Manifest.permission.BLUETOOTH_ADMIN);

    if(bluetoothGranted == PackageManager.PERMISSION_GRANTED &&
            bluetoothAdminGranted == PackageManager.PERMISSION_GRANTED) {
        granted = true;
    }

    return granted;
}

If required permission is not granted, here's how you would ask for it:

@RequiresApi(api = Build.VERSION_CODES.M)
private void askForBluetoothPermissions() {
    String[] permissions = new String[] {
            Manifest.permission.BLUETOOTH,
            Manifest.permission.BLUETOOTH_ADMIN
    };
    requestPermissions(permissions, PERMISSION_ASK);
}

And finally, here's how you would confirm if the user granted you the permission(s) or not:

@Override
public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions, @NonNull int[] grantResults) {
    switch (requestCode) {
        case PERMISSION_ASK:
            if(grantResults[0] == PackageManager.PERMISSION_GRANTED && grantResults[1] == PackageManager.PERMISSION_GRANTED) {
                // all requested permissions were granted
                // perform your task here
            } else {
                // permissions not granted
                // DO NOT PERFORM THE TASK, it will fail/crash
            }
            break;
        default:
            super.onRequestPermissionsResult(requestCode, permissions, grantResults);
            break;
    }
}

Hope this helps

Google's new motto: "Turning one line of code into a hundred, since 2008." — Kevin Krumwiede, Oct 23 '16 at 01:23
@KevinKrumwiede I see what you mean but look at it this way, at least the option is there. iOS doesn't even allow non-system application to turn on WiFi or simple features like that. Android is used on so many different systems at so many different version levels. Of course, more work will be required. iOS is built for one phone. Not many options there — ᴛʜᴇᴘᴀᴛᴇʟ, Oct 23 '16 at 01:35
I'm comparing this to earlier versions of Android, not iOS. Google is always looking for ways to make simple things harder, and runtime permissions were a totally uncalled-for misfeature. I'm simply not targeting 6+ until Google comes to its senses. — Kevin Krumwiede, Oct 23 '16 at 04:18
Idk. I personally wouldn't called it ubcalled-for misfeature. The feature is the ability to grant and deny permission from the user perspective. Not the fact that it makes developer life easy/hard — ᴛʜᴇᴘᴀᴛᴇʟ, Oct 23 '16 at 04:55
My target android version is lollipop, so when I tried this it did not work — ComputerGeek101, Oct 23 '16 at 18:05

score 4 · Accepted Answer · answered Oct 26 '16 at 14:01

4

You only need <uses-permission> tag since you are using a permission. You don't need <permissions> tag since this is not your custom permission.
Maybe you have placed <uses-permission> tag in the wrong element in manifest, but I cannot say anything else with the information you provided
Since your bluetoothAdapter can be null, either add to second IF null pointer check, or add a RETURN in first IF
It is also nice to have <uses-feature> tag

answered Oct 26 '16 at 14:01

Drez

488
3
10

1

thanks, I accidentally put my permissions in the application tags. – ComputerGeek101 Nov 04 '16 at 01:03

score 1 · Answer 3 · answered Jun 02 '19 at 18:48

For Android 6.0 and above you must add the following to manifest file

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

<permission android:name="android.permission.BLUETOOTH" android:label="BLUETOOTH" />
<permission android:name="android.permission.BLUETOOTH_ADMIN" />
<permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

missing permissions required by BluetoothAdapter.isEnabled.BLUETOOTH

3 Answers3