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
On Android when the application is in background, after a certain delay the OS will close every connection with informing about it.
@@ -611,7 +646,7 @@ class RNCallKeepExample extends React.Component {
611
646
## Receiving a call when the application is not reachable.
612
647
613
648
In some case your application can be unreachable :
614
-
- when the user kill the application
649
+
- when the user kill the application
615
650
- when it's in background since a long time (eg: after ~5mn the os will kill all connections).
616
651
617
652
To be able to wake up your application to display the incoming call, you can use [https://github.com/ianlin/react-native-voip-push-notification](react-native-voip-push-notification) on iOS or BackgroundMessaging from [react-native-firebase](https://rnfirebase.io/docs/v5.x.x/messaging/receiving-messages#4)-(Optional)(Android-only)-Listen-for-FCM-messages-in-the-background).
@@ -626,13 +661,14 @@ Since iOS 13, you'll have to report the incoming calls that wakes up your applic
// NSDictionary *extra = [payload.dictionaryPayload valueForKeyPath:@"custom.path.to.data"]; /* use this to pass any special data (ie. from your notification) down to RN. Can also be `nil`*/
@@ -646,6 +682,9 @@ Since iOS 13, you'll have to report the incoming calls that wakes up your applic
646
682
adb logcat *:S RNCallKeepModule:V
647
683
```
648
684
685
+
## Troubleshooting
686
+
- Ensure that you construct a valid `uuid` by importing the `uuid` library and running `uuid.v4()` as shown in the examples. If you don't do this and use a custom string, the incoming call screen will never be shown on iOS.
687
+
649
688
## Contributing
650
689
651
690
Any pull request, issue report and suggestion are highly welcome!
0 commit comments