Open vuletuan opened 3 years ago
Same issue here; after enabling it a few times it then stays persistent enabled.
Same issue here; after enabling it a few times it then stays persistent enabled.
it seems to be a Samsung bug. I updated to the newest version then it worked.
Hello, I also have this issue Do you have any update ?
Hello, I also have this issue Do you have any update ?
My device's working well. Just update to the latest android version (11) and One UI (3.1).
i have same issue, samsung galaxy a50 android 11 one UI 3.1, still got this issue, please help
Same issue is occurring on Samsung A020 having android 11. Please keep updated
In my case, Calling Account needs Phone permission before enable it.
I have to add these to the AndroidManifest.xml following Phone numbers
<uses-permission android:name="android.permission.READ_PHONE_STATE" android:maxSdkVersion="29" /> <uses-permission android:name="android.permission.READ_PHONE_NUMBERS" />
On option I need to add
additionalPermissions: [PERMISSIONS.ANDROID.READ_PHONE_STATE, PERMISSIONS.ANDROID.READ_PHONE_NUMBERS]
When calling RNCallKeep.setup(options), the library will ask for those permissions. After I granted Phone permission, Calling Account is permanent enabled.
I have the same issue too. My phone also updated that latest version. But the issue hasn't been resolved. Do you have any solutions for this case?
This is happening on Samsung S10 Android 12, anyone figured this out?
@huynextlevel have you been able to fix this? I've seen that you've figured this out in the other thread https://github.com/react-native-webrtc/react-native-callkeep/issues/512 did your solution address it? Could you please provide your fix?
I was facing this issue and had to spend hours debugging the call keep native code only to find out that I was missing one permission in my Android Manifest file which is not mentioned in the documentation or at least I could not find it. The permission was for recording audio.
Please add the following line in your AndroidManifest.xml file,
<uses-permission android:name="android.permission.RECORD_AUDIO" />
@mayur-bhandari I think the issue here is with "calling accounts" persisting on Android. Not sure if it's a samsung specific bug, but seems like when "calling account" permission is given, which corresponds to "registerPhoneAccount" permission. It is not persisted, rather it keeps toggling back off
I was facing this issue and had to spend hours debugging the call keep native code only to find out that I was missing one permission in my Android Manifest file which is not mentioned in the documentation or at least I could not find it. The permission was for recording audio.
Please add the following line in your AndroidManifest.xml file,
<uses-permission android:name="android.permission.RECORD_AUDIO" />
it's works for me and I also provide some permission manually from app info.
I am using realme 7i (android version 11) and in my case, when it requests for the permission and i open the settings (click ok on the alert), there is no option shown for adding my app. I manually checked from the settings too but there is completely no option which mentions calling account apps. BTW, all the other required permissions are enabled.
I am using realme 7i (android version 11) and in my case, when it requests for the permission and i open the settings (click ok on the alert), there is no option shown for adding my app. I manually checked from the settings too but there is completely no option which mentions calling account apps. BTW, all the other required permissions are enabled.
my problem is same. my device is realme 9i
Bug report
Description
After installation, I requested calling account permission then enable it. Back to the home screen, I can receive calls at all. After that, I kill the app then open the app again but it still shows a pop-up to enable a calling account. I repeat all steps above, but the app still requests calling account. It just happened on android 11. On Android 9, 10 it works fine
Steps to Reproduce
Versions