Skip to content

feat(react-native): reject call when busy #1856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 35 commits into
base: main
Choose a base branch
from
Open

Conversation

kristian-mkd
Copy link
Contributor

@kristian-mkd kristian-mkd commented Jul 18, 2025

💡 Overview

Adds support in the react-native SDK for automatically rejecting a call with reason busy when the callee is in another call, so that integrators can implement handing of the callee busy scenario.

📝 Implementation notes

Adds shouldRejectCallWhenBusy props in React Native push notifications configuration. (false by default)

Handles the call rejection case in the sample app with:

  • showing toast message: Call rejected because user is busy.
  • playing busy tone

🎫 Ticket: https://linear.app/stream/issue/RN-232

📑 Docs: https://github.com/GetStream/docs-content/pull/476

@kristian-mkd kristian-mkd marked this pull request as draft July 18, 2025 11:15
@kristian-mkd kristian-mkd marked this pull request as ready for review July 21, 2025 17:38
@kristian-mkd kristian-mkd changed the title feat(react-native): busy tone feat(react and react-native): busy tone Jul 22, 2025
@kristian-mkd kristian-mkd changed the title feat(react and react-native): busy tone feat(react&react-native): busy tone Jul 22, 2025
@kristian-mkd kristian-mkd changed the title feat(react&react-native): busy tone feat(react&react-native): reject user when busy Jul 22, 2025
@kristian-mkd kristian-mkd changed the title feat(react&react-native): reject user when busy feat(react&react-native): reject call when busy Jul 22, 2025
@kristian-mkd kristian-mkd changed the title feat(react&react-native): reject call when busy feat(react-native): reject call when busy Jul 23, 2025
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change absolutely necessary?

it seems like we are informing integrators to handle this on their own to not show incoming call component

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants