[Bug]: Tapping outside Android location permission dialog results in `LocationPermission.deniedForever` about flutter-geolocator

[TimHoogstrate]

Dear @lukehutch,

Unfortunately, this is a known edge case. How it works is explained in the documentation:
I'll close this issue for now, feel free to reopen the issue if new information pops-up.

  /**
     * Returns a {@link PermissionConstants} for a given permission.
     * <p>
     * When {@link PackageManager#PERMISSION_DENIED} is received, we do not know if the permission was
     * denied permanently. The OS does not tell us whether the user dismissed the dialog or pressed
     * 'deny'. Therefore, we need a more sophisticated (read: hacky) approach to determine whether the
     * permission status is {@link PermissionConstants#PERMISSION_STATUS_DENIED} or
     * {@link PermissionConstants#PERMISSION_STATUS_NEVER_ASK_AGAIN}.
     * <p>
     * The OS behavior has been researched experimentally and is displayed in the following diagrams:
     * <p>
     * State machine diagram:
     * <p>
     * Dismissed
     *    ┌┐
     * ┌──┘▼─────┐  Granted ┌───────┐
     * │Not asked├──────────►Granted│
     * └─┬───────┘          └─▲─────┘
     *   │           Granted  │
     *   │Denied  ┌───────────┘
     *   │        │
     * ┌─▼────────┴┐        ┌────────────────────────────────┐
     * │Denied once├────────►Denied twice(permanently denied)│
     * └──▲┌───────┘ Denied └────────────────────────────────┘
     *    └┘
     * Dismissed
     * <p>
     * Scenario table listing output of
     * {@link ActivityCompat#shouldShowRequestPermissionRationale(Activity, String)}:
     * ┌────────────┬────────────────┬─────────┬───────────────────────────────────┬─────────────────────────┐
     * │ Scenario # │ Previous state │ Action  │ New state                         │ 'Show rationale' output │
     * ├────────────┼────────────────┼─────────┼───────────────────────────────────┼─────────────────────────┤
     * │ 1.         │ Not asked      │ Dismiss │ Not asked                         │ false                   │
     * │ 2.         │ Not asked      │ Deny    │ Denied once                       │ true                    │
     * │ 3.         │ Denied once    │ Dismiss │ Denied once                       │ true                    │
     * │ 4.         │ Denied once    │ Deny    │ Denied twice (permanently denied) │ false                   │
     * └────────────┴────────────────┴─────────┴───────────────────────────────────┴─────────────────────────┘
     * <p>
     * To distinguish between scenarios, we can use
     * {@link ActivityCompat#shouldShowRequestPermissionRationale(Activity, String)}. If it returns
     * true, we can safely return {@link PermissionConstants#PERMISSION_STATUS_DENIED}. To distinguish
     * between scenarios 1 and 4, however, we need an extra mechanism. We opt to store a boolean
     * stating whether permission has been requested before. Using a combination of checking for
     * showing the permission rationale and the boolean, we can distinguish all scenarios and return
     * the appropriate permission status.
     * <p>
     * Changing permissions via the app info screen, so outside of the application, changes the
     * permission state to 'Granted' if the permission is allowed, or 'Denied once' if denied. This
     * behavior should not require any additional logic.
     *
     * @param activity       the activity for context
     * @param permissionName the name of the permission
     * @param grantResult    the result of the permission intent. Either
     *                       {@link PackageManager#PERMISSION_DENIED} or {@link PackageManager#PERMISSION_GRANTED}.
     * @return {@link PermissionConstants#PERMISSION_STATUS_GRANTED},
     * {@link PermissionConstants#PERMISSION_STATUS_DENIED}, or
     * {@link PermissionConstants#PERMISSION_STATUS_NEVER_ASK_AGAIN}.
     */

[sachinkhatripro]

I am also facing this problem.

[sachinkhatripro]

Permission.location.status may instead be used.

[lukehutch]

@TimHoogstrate How about adding one additional catch-all -- that if Geolocator.requestPermission() returns within some short period of time (e.g. 100ms), then the status is set to permanently denied?

Actually it would be great if Geolocator could distinguish between "known permanently denied" (if Geolocator.requestPermission() returns immediately) and "may be permanently denied"...