react-native-webrtc / react-native-webrtc/react-native-callkeep
Google rejects the app with RNCallkeep
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
-
iOS
Description
Hi!
I am using three RNCallkeep methods: display incoming call, accept call, decline call.
The main functionality is that I just display a notification as incoming call, and can accept or decline. For the moment I do not need more functions.
I pasted these permissions requiests in AndroidManifest file as by documents of rncallkeep.

Google requires to explain why I use these permissions in the app with selecting some of the options. I selected "Default Call" as it is the closest option to the functionality I have.
It says I also have request for SMS and have to explain that. App got rejected because functionality of the app does not correspond to the selected option.
Question: what to do? What to select on Google? and maybe I do not need all the permissions requests here? Thanks for help!
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 RNCallkeep documentation and example, then inspect the AndroidManifest permissions referenced in the report. Compare those permissions with Google's app policy requirements and determine which declarations are required for the described incoming-call flow. Done means documenting the minimal permissions and the appropriate policy explanation or selection.
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