Skip to content
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

How to handle calls when the app is killed? #143

Open
anniewey opened this issue Feb 4, 2022 · 1 comment
Open

How to handle calls when the app is killed? #143

anniewey opened this issue Feb 4, 2022 · 1 comment

Comments

@anniewey
Copy link

anniewey commented Feb 4, 2022

Hi, I'm having trouble connecting calls when app is killed. As I'm using OneSignal for notification, I had no idea how to sync the call with notification which is needed to trigger the app to open.

When app is in bg, I used react-native-invoke-app to bring the app back to fg. But when the app is killed, I'm not sure how to trigger the app to launch and connect to the client.

The client returned 480 error almost immediately after the call is initiated. How do I handle calls in this scenario?

call: Call {_VICallConnectedCallback: ƒ, _VICallDisconnectedCallback: ƒ, _VICallEndpointAddedCallback: ƒ, _VICallFailedCallback: ƒ, _VICallICETimeoutCallback: ƒ, …}
code: 480
headers: {X-VI-Hangup-Cause: 'Normal termination'}
name: "Failed"
reason: "Temporarily Unavailable"
@michaeldadi
Copy link

+1

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

No branches or pull requests

2 participants