react-native-webrtc / react-native-webrtc/react-native-callkeep
Android permission android.permission.CALL_PHONE lost between restarts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
Android
Description
This permission is required to receive incoming calls. It the phone is restarted, unless the app is launched again, the permission is lost.
Steps to Reproduce
const options = {
ios: {
appName: 'Sylk',
maximumCallGroups: 1,
maximumCallsPerCallGroup: 2,
supportsVideo: true,
includesCallsInRecents: true,
imageName: "Image-1"
},
android: {
alertTitle: 'Calling account permission',
alertDescription: 'Please allow Sylk inside All calling accounts',
cancelButton: 'Deny',
okButton: 'Allow',
imageName: 'phone_account_icon',
additionalPermissions: [PermissionsAndroid.PERMISSIONS.CAMERA, PermissionsAndroid.PERMISSIONS.RECORD_AUDIO, PermissionsAndroid.PERMISSIONS.READ_CONTACTS]
}
};
Launch your app. Enable calling permission as requested by this.RNCallKeep.setup(options);
Enable the Calling account in all calling account section when prompted.
Restart the phone.
Go to Call interface -> Touch top right ... -> Settings -> Calling accounts
The account has vanished. You must start the app again in order to enable the CALL_PHONE permission.
Versions
- Callkeep: nimbleape/react-native-callkeep-1#aaf508332ff0855f500bd522779ef87884b59621
- React Native: 0.61.5
- iOS:
- Android: 9 or 10
- Phone model: Any
Logs
Nothing relevant in the logs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked example and the RNCallKeep.setup(options) flow on Android 9 or 10, reproducing the restart sequence described in the issue. Trace how the CALL_PHONE permission and calling account are initialized, then verify that the account remains enabled after a phone restart without relaunching the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100