[Bug]: Callbacks like onGrantedCallback does not work as expected.

[ebsangam]

Please check the following before submitting a new issue.

• I have searched the existing issues.
• I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

• Android
• iOS
• Windows

Steps to reproduce

1. Use a callback Permission.contacts.onGrantedCallback
2. Grant permission for camera.
3. Permission.contacts.onGrantedCallback will be invoked.

Expected results

When using Permission.contacts.onGrantedCallback we expect this callback to invoke only if we grant permission for contacts.

Actual results

No mater what permission you add callback it will always gets invoked for every permission.

Code sample

Code sample

Permission.contacts.onGrantedCallback(
  () {
    print('Contacts permission granted.');
  },
);

Screenshots or video

Screenshots or video demonstration

[Upload media here]

Version

11.0.1

Flutter Doctor output

Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.6.1 23G93 darwin-arm64, locale en-NP)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.95.3)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

[TimHoogstrate]

Dear @ebsangam,

Can you elaborate a bit on the subject? Are you testing this in iOS or Android? And what version of OS?

Kind regards,

[ebsangam]

I was testing on Android emulator SDK 34. I wanted to listen to contacts permission status change (on granted to be specific). So I used Permission.contacts.onGrantedCallback. But the callback gets invoked when I grant camera permission or microphone permission. Basically Permission.contacts.onGrantedCallback is not only listening to contacts permission updated but for every permission updates. Thanks.

[12people]

@TimHoogstrate

Running into the same issue. (Only tried building on Android so far, but I imagine all the platforms have this error.)

Here's a full flutter app code to replicate it:

import 'package:flutter/material.dart';

import 'package:permission_handler/permission_handler.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatefulWidget {
  const MainApp({super.key});

  @override
  State<MainApp> createState() => _MainAppState();
}

class _MainAppState extends State<MainApp> {
  PermissionStatus? locationState;
  PermissionStatus? notificationState;

  @override
  Widget build(BuildContext context) {
    const locationPermission = Permission.locationAlways;
    locationPermission.onDeniedCallback(() {
      setState(() => locationState = PermissionStatus.denied);
    });
    locationPermission.onGrantedCallback(() {
      setState(() => locationState = PermissionStatus.granted);
    });
    locationPermission.onLimitedCallback(() {
      setState(() => locationState = PermissionStatus.limited);
    });
    locationPermission.onPermanentlyDeniedCallback(() {
      setState(() => locationState = PermissionStatus.permanentlyDenied);
    });
    locationPermission.onProvisionalCallback(() {
      setState(() => locationState = PermissionStatus.provisional);
    });
    locationPermission.onRestrictedCallback(() {
      setState(() => locationState = PermissionStatus.restricted);
    });

    const notificationPermission = Permission.notification;
    notificationPermission.onDeniedCallback(() {
      setState(() => notificationState = PermissionStatus.denied);
    });
    notificationPermission.onGrantedCallback(() {
      setState(() => notificationState = PermissionStatus.granted);
    });
    notificationPermission.onLimitedCallback(() {
      setState(() => notificationState = PermissionStatus.limited);
    });
    notificationPermission.onPermanentlyDeniedCallback(() {
      setState(() => notificationState = PermissionStatus.permanentlyDenied);
    });
    notificationPermission.onProvisionalCallback(() {
      setState(() => notificationState = PermissionStatus.provisional);
    });
    notificationPermission.onRestrictedCallback(() {
      setState(() => notificationState = PermissionStatus.restricted);
    });

    return MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: Center(
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              children: [
                for (final permissionEntry
                    in {
                      locationPermission: locationState,
                      notificationPermission: notificationState,
                    }.entries)
                  Column(
                    mainAxisSize: MainAxisSize.min,
                    children: [
                      Text("${permissionEntry.key}: ${permissionEntry.value}"),
                      TextButton(
                        onPressed: () {
                          permissionEntry.key.request();
                        },
                        child: Text("REQUEST ${permissionEntry.key}"),
                      ),
                    ],
                  ),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

Of course, you'll need to add the requisite permissions to Android manifest as well, and add permission_handler to pubspec.yaml as well:

<!-- Permissions options for the `access notification policy` group -->
    <uses-permission android:name="android.permission.ACCESS_NOTIFICATION_POLICY"/>

    <!-- Permissions options for the `notification` group -->
    <uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>

    <!-- Permissions options for the `location` group -->
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />

  permission_handler: ^11.4.0

[12people]

Here's a recording of the odd behavior:

error-recording.mp4

(Same code as I posted above.)

[12people]

As for my Android version, it's Android 13 (build 6.A.031.7).

[TimHoogstrate]

@12people,

Requesting the permission works fine (also in the example app), you can check it in the app settings after requesting and approving the permissions. However, your demo app is just presenting the results wrongly. Try to keep the registration of the callbacks outside of the build method.

@ebsangam I've verified that is works properly in the example app.

Kind regards,

[ebsangam]

@12people,

Requesting the permission works fine (also in the example app), you can check it in the app settings after requesting and approving the permissions. However, your demo app is just presenting the results wrongly. Try to keep the registration of the callbacks outside of the build method.

@ebsangam I've verified that is works properly in the example app.

Kind regards,

I think you misunderstood the issue. Let's not focus on the example app instead my original issue I mentioned. It is the issue about callback that fires unnecessarily.

[TimHoogstrate]

Dear @ebsangam,

Still I cannot reproduce this. Please provide me with a clear sample. Again, I tested this but I cannot reproduce this. The sample of @12people is just not working properly. If I change any of the permissions from Permission.notification to another (for example contacts I get the same results (only then with .contacts).

Kind regards,

[ebsangam]

I will provide you a minimal reproducible code when I am free.