Flutter iOS Calling App Troubleshooting
Budget: $250 – $750 AUD
Hi, we are experiencing an issue with our Flutter mobile app for iOS, which uses IP calls as its primary functionality. When the app is in the background, off, and killed state, incoming calls are not received, although everything functions correctly when the app is open and active. We need assistance in identifying the root cause of this behavior and resolving it.
Currently, we are using Janus WebRTC for making and receiving calls: https://janus.conf.meetecho.com/.
The app works flawlessly on Android, and on iOS it performs well for foreground calls. However, on iOS, incoming calls fail to reach the app when it is in the background and killed state.
Although push notifications for calls do reach the app on iOS, the calls themselves do not come through. It appears that FCM may not be fully compatible with iOS for call functionality due to iOS background restrictions. Instead, using an APN token with VoIP might be necessary to wake the app especially when it is in the killed state and running in the background.
For our database services, we are using Firebase.
If you have experience resolving and developing similar applications, please let us know so we can discuss this further. It would be extremely helpful if you could provide a technical explanation of how you would address these issues.
Currently, we are using Janus WebRTC for making and receiving calls: https://janus.conf.meetecho.com/.
The app works flawlessly on Android, and on iOS it performs well for foreground calls. However, on iOS, incoming calls fail to reach the app when it is in the background and killed state.
Although push notifications for calls do reach the app on iOS, the calls themselves do not come through. It appears that FCM may not be fully compatible with iOS for call functionality due to iOS background restrictions. Instead, using an APN token with VoIP might be necessary to wake the app especially when it is in the killed state and running in the background.
For our database services, we are using Firebase.
If you have experience resolving and developing similar applications, please let us know so we can discuss this further. It would be extremely helpful if you could provide a technical explanation of how you would address these issues.