They are both called by the PermissionsHelper:

We can't remove onRequestPermissionResult until the next major version because it will break existing plugins that haven't been updated to use onRequestPermissionsResult.

Where does callback.first.onRequestPermissionResult in CordovaInterfaceImpl call to?

CordovaInterfaceImpl is directly calling the deprecated method onRequestPermissionResult but the deprecation annotation is pushing developers to override the new method that is never executed.

Also, does it make sense for the PermissionHelper to execute both the deprecated and the new methods? That seems like a source of bugs lurking around for plugins as it isn't explicit that both will be executed and mainly because PermissionHelper is to provide back compatibility with potentially legacy code.

@dpogue

They are both called by the PermissionsHelper:

This isn't really correct though, this method is private and never called by anything that I can see.

There's essentially no way to have onRequestPermissionResults be called.

@gwynjudd I think the deliverPermissionResult method is deprecated and can be removed.

If I remember correctly, this helper class originated from Apache's cordova-plugin-compat plugin. That plugin is deprecated long ago. Its version of the helper class had and used the deliverPermissionResult method.

I believe the class was copied to this repo to make it available for other plugins and was a part of Cordova-Android 5 backward compatibility support. #594

Removing onRequestPermissionResult may break existing plugins.

Even though Apache has added the deprecated flag and updated Apache core plugins to not use the method, many unmaintained third-party plugins works with the current version of Cordova-Android and could be calling the deprecated method. If we remove the method, then all those plugins will stop working.

There might have been some agreement that this step has to be taken either way, but when?

I've just spent a day adding POST_NOTIFICATIONS permission to a plugin that didn't previously need permissions, and have run across this issue.

If you override onRequestPermissionsResult (the new method) in your plugin, it does not work. That method is not called when the user picks an option on the permissions dialog (or swipes to dismiss).

To actually get called back, you have to override the deprecated method onRequestPermissionResult.

The documentation correctly tells you to use the old deprecated method name. I was surprised to find that Android Studio struck through the method name indicating that it was deprecated. I changed it to the new name, then wasted a lot of time wondering why it didn't work until I realised that the callback wasn't even called.

In my project, nothing calls PermissionsHelper.deliverPermissionResult. Indeed, since it is a private method in PermissionHelper, the only way it could be called is through reflection. It seems highly unlikely that anyone would do that, since you can simply call onRequestPermissionsResult yourself directly. The purpose of this code was to call the callback on Android versions that didn't support the requestPermissions API, but since the minimum supported Android version is now 7.0 (SDK 24), the requestPermission/s methods no longer need to implement a workaround.

Suggested fixes:

1. Revert feat: Deprecated onRequestPermissionResult in favour for onRequestPermissionsResult for consistency #1047 and live with the inconsistency, OR
2. Add a call to callback.first.onRequestPermissionsResult to CordovaInterfaceImpl.onRequestPermissionResult, after the call to callback.first.onRequestPermissionResult. Update the documentation to the new method.

I also suggest that PermissionsHelper.deliverPermissionResult is removed.

As an alternative, we could make CordovaPlugin.onRequestPermissionsResult (the new method's default implementation) call CordovaPlugin.onRequestPermissionResult (the old method, which may be overridden in plugins). Then change CordovaInterfaceImpl to only call callback.first.onRequestPermissionsResult (i.e. the new method).

// CordovaPlugin.java

    /**
     * Called by the system when the user grants permissions
     *
     * @param requestCode
     * @param permissions
     * @param grantResults
     * 
     * @deprecated Use {@link #onRequestPermissionsResult} instead.
     */
    @Deprecated
    public void onRequestPermissionResult(int requestCode, String[] permissions,
                                          int[] grantResults) throws JSONException {

    }

    /**
     * Called by the system when the user grants permissions
     *
     * @param requestCode
     * @param permissions
     * @param grantResults
     */
    public void onRequestPermissionsResult(int requestCode, String[] permissions,
                                          int[] grantResults) throws JSONException {
        // Call the old method name for backward compatibility
        this.onRequestPermissionResult(requestCode, permissions, grantResults);
    }

/// CordovaInterfaceImpl.java

    /**
     * Called by the system when the user grants permissions
     *
     * @param requestCode
     * @param permissions
     * @param grantResults
     */
    public void onRequestPermissionResult(int requestCode, String[] permissions,
                                          int[] grantResults) throws JSONException {
        Pair<CordovaPlugin, Integer> callback = permissionResultCallbacks.getAndRemoveCallback(requestCode);
        if(callback != null) {
            callback.first.onRequestPermissionsResult(callback.second, permissions, grantResults);
        }
    }

It may be worth renaming the method in CordovaInterface (therefore also CordovaInterfaceImpl) for consistency.