react-native-webrtc / react-native-webrtc/react-native-callkeep
Permission to Use Android's Telecom Connection Service Denied
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 https://github.com/react-native-webrtc/react-native-callkeep to reproduce the issue.
-
Reproduced on:
-
Android
Description
I use wazo call connection service but in some devices it doesn't ask for permission .In some of devices Phone Account is also not find where an user enable it.
Versions
- Callkeep:
- React Native:
- Android:
- Phone model:
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 Android manifest service declaration shown for io.wazo.callkeep.VoiceConnectionService and reproduce the missing permission or Phone Account on the affected devices. Collect the missing Callkeep, React Native, Android, and phone model versions, then verify that the service is discoverable and the required permission flow works on those devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, 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