You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The incoming calls come through in any state on both devices — the issue is with showing the correct type of notification and then launching the app on that notification.
So, the problem is that when the app is killed:
-- on iOS an incoming call notification launches the app, this is what we need, and on launch I’m just checking if there are any pending calls, to show the correct UI screen, it seems working fine. It is similar to WhatsApp behaviour. Is it correct implementation?
-- on Android, an incoming call notification doesn’t open the app and is not a full-screen notification. 1. The question is how to make the incoming call notification be full-screen and launch the app on Android in order to show the correct UI screen?
And another question: 2. do I need to integrate any Push Notifications package to our React Native app to manage Twilio notifications or is it handled completely by the Twilio React Native SDK package?
Reproduction Steps
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected Behavior
A clear and concise description of what you expected to happen.
Actual Behavior
What actually happens.
Reproduction Frequency
Is the reproducibility of the issue deterministic? If not, what percentage of the time does the issue occur? In how many attempts was the issue observed?
Screenshots
If applicable, add screenshots to help explain your problem.
Software and Device Information
Please complete the following information.
Device: [e.g. iPhone 12, Pixel 3]
OS: [e.g. iOS 16, Android API Level 31]
React version: [e.g. 18.1.0]
React Native version: [e.g. 0.70.9]
Node version: [e.g. 16.18.1]
npm or yarn version: [e.g. 8.19.2, 1.22.19]
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
On Android, we are using the system provided "Call Notification". I believe if you tap on the notification (outside of the buttons), it will launch the app. You can read more about the notification here. You can change this behavior but it requires you to make changes to make changes to this SDK and be familiar with Java.
No, don't integrate the ReactNative Push Notifications package to your app, it may break your ability to receive incoming calls.
Issue
Pre-submission Checklist
or sensitive account information (API keys, credentials, etc.) when reporting this issue.
Description
The incoming calls come through in any state on both devices — the issue is with showing the correct type of notification and then launching the app on that notification.
So, the problem is that when the app is killed:
-- on iOS an incoming call notification launches the app, this is what we need, and on launch I’m just checking if there are any pending calls, to show the correct UI screen, it seems working fine. It is similar to WhatsApp behaviour. Is it correct implementation?
-- on Android, an incoming call notification doesn’t open the app and is not a full-screen notification. 1. The question is how to make the incoming call notification be full-screen and launch the app on Android in order to show the correct UI screen?
And another question: 2. do I need to integrate any Push Notifications package to our React Native app to manage Twilio notifications or is it handled completely by the Twilio React Native SDK package?
Reproduction Steps
Expected Behavior
A clear and concise description of what you expected to happen.
Actual Behavior
What actually happens.
Reproduction Frequency
Is the reproducibility of the issue deterministic? If not, what percentage of the time does the issue occur? In how many attempts was the issue observed?
Screenshots
If applicable, add screenshots to help explain your problem.
Software and Device Information
Please complete the following information.
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: