Android 11 - setting RNCallkeep.setCurrentCallActive(uuid) causes the native call state to update in self Managed mode, but it should not.

Bug report

• [*] I've checked the example to reproduce the issue.

• Reproduced on:

• [*] Android

• iOS

Description

In Android 11, setting RNCallkeep.setCurrentCallActive(uuid) causes the native call state to update in self Managed mode, but it should not.

Steps to Reproduce

I am using react-native-callkeep
library to handle my VOIP calls and GSM calls interoperability in my react native application.

Have followed this installation and setup guide for RNCallkeep and some chunks of this example for the implementation.

Also using react-native-call-detection for getting the native call states, to do some action on existing VOIP calls in case of native call interruptions.

However, in Android 11, setting RNCallkeep.setCurrentCallActive(uuid) causes the native call state to update in self Managed "true" mode, but it should not.

Versions

- Callkeep: 4.3.1
- React Native: 0.62.3
- Android: 11
- Phone model: all

Logs

Paste here

Start with the example and docs/android-installation.md, then trace RNCallkeep.setCurrentCallActive(uuid) through the Android implementation while reproducing on Android 11 in self Managed mode. Done means the native call state no longer changes when this method is used in self Managed mode; the issue provides no logs or test file, so reproduction and regression coverage must be established first.