# Incoming call notification is not coming

**URL:** <https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846>\
**Category:** React Native\
**Created:** [November 1, 2022, 5:33am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846 "2022-11-01T05:33:25Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![itruck008](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/itruck008/32/3215_2.png) [@itruck008](https://community.sendbird.com/u/itruck008)\
**Post date:** [November 1, 2022, 5:33am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/1 "2022-11-01T05:33:25Z")

</div>

**Incoming call notification not coming**  
When I am making a call from one device to another on receiver side incoming call notification is not coming only missed call notification is coming. One of my another developer is also using the same code but on their system code is working fine. So I just want to know that is there any environment settings that I need to check/configure in my system?

---

<div class="post-metadata">

**Author:** ![Brian\_Sang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/brian_sang/32/1228_2.png) [@Brian\_Sang](https://community.sendbird.com/u/Brian_Sang)\
**Post date:** [November 2, 2022, 5:00am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/2 "2022-11-02T05:00:55Z")

</div>

Hello,

For iOS and Android, could you check if the push cert and device push token are registered normally?

> **[Add push notifications | Calls React Native SDK | Sendbird Docs](https://sendbird.com/docs/calls/v1/react-native/direct-call/adding-push-notifications/add-push-notifications#1-add-push-notifications)**
>
> After you have authenticated the client app and the user, set up notifications and register
> push tokens for the user to receive push notifications on the device. Push tokens allow the client app to receive notifications about an incoming 1-to-1 call...

Which device has the problem and which device hasn’t?

---

<div class="post-metadata">

**Author:** ![itruck008](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/itruck008/32/3215_2.png) [@itruck008](https://community.sendbird.com/u/itruck008)\
**Post date:** [November 4, 2022, 4:59am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/3 "2022-11-04T04:59:32Z")

</div>

Thank you for the reply. I think it’s not an FCM problem, but this is an issue regarding that the call reception is not working in most PC emulator environments.

It is not related to FCM because FCM missed call notification works fine after the call ends. Also, the call reception works fine when test-distributed on google console and when the apk is built and installed in real device.

The problem is that the call reception is not working ONLY in the develpment environment.

Below is the list of test situation that we have went through so far:

1. Only 1 PC can receive calls on the android emulator, among 6 different PCs. (Tried in the same branch of GitHub, so it is not the issue of RN code)
2. The other 5 PCs cannot receive calls on both Emulator in PC (virtual) and physical device.
3. The reception works well when apk is built and installed on a real device. However, in this case, the log of the modified code cannot be checked in real time, and the apk must be built and installed on the actual device after each and every modification.
4. Call reception works even when test-deployed in google play store.
5. It is not an android studio version problem.
6. Device: nexus5X (or 5) API 30 / pixel XL API 33
7. It’s not a npm or node version issue.
8. It’s not a library version problem in react native.
9. It’s not a Windows 10 or 11 version issue either.
10. I have tried - clean project, rebuild project, invalidate caches, wipe data, cold boot in android studio, but nothing worked.

Other than the above issues, is there any other steps that we need to check/follow when setting up the development environment for RN - Android Emulator?

---

<div class="post-metadata">

**Author:** ![Airen\_Kang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/airen_kang/32/1831_2.png) [@Airen\_Kang](https://community.sendbird.com/u/Airen_Kang)\
**Post date:** [November 4, 2022, 9:29am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/4 "2022-11-04T09:29:53Z")

</div>

Hi @itruck008, could you check if the emulators are Google APIs enabled?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/sendbird/original/2X/f/f6230ec2be19c2429054b99c03b39ba6d7aae98f.png)

---

<div class="post-metadata">

**Author:** ![itruck008](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/itruck008/32/3215_2.png) [@itruck008](https://community.sendbird.com/u/itruck008)\
**Post date:** [November 7, 2022, 4:59am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/6 "2022-11-07T04:59:38Z")

</div>

We’re using the beta version of Sendbird may be this issue is because of that, so is there any better way to migrate this to official SDK with minimal changes?

> **[react-native-sendbird-calls](https://www.npmjs.com/package/react-native-sendbird-calls)**
>
> TODO. Latest version: 1.0.0-beta7, last published: 6 months ago. Start using react-native-sendbird-calls in your project by running \`npm i react-native-sendbird-calls\`. There are no other projects in the npm registry using...

> **[GitHub - tamhv/react-native-sendbird-calls](https://github.com/tamhv/react-native-sendbird-calls)**
>
> Contribute to tamhv/react-native-sendbird-calls development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Airen\_Kang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/airen_kang/32/1831_2.png) [@Airen\_Kang](https://community.sendbird.com/u/Airen_Kang)\
**Post date:** [November 8, 2022, 4:11am UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/7 "2022-11-08T04:11:50Z")

</div>

Hi @itruck008.  
That is not our beta SDK, and not many APIs are supported, so it seems there will be no big problem even if you migrate them manually.

Our official SDK is here [@sendbird/calls-react-native - npm](https://www.npmjs.com/package/@sendbird/calls-react-native)  
[GitHub - sendbird/sendbird-calls-react-native: Sendbird Calls SDK for React-Native](https://github.com/sendbird/sendbird-calls-react-native)

Thanks!

---

<div class="post-metadata">

**Author:** ![itruck008](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/itruck008/32/3215_2.png) [@itruck008](https://community.sendbird.com/u/itruck008)\
**Post date:** [November 11, 2022, 1:15pm UTC](https://community.sendbird.com/t/incoming-call-notification-is-not-coming/5846/8 "2022-11-11T13:15:06Z")

</div>

Incoming calls are coming now. We’re using wrong firebase server key for dev project. It is working now.
