[feature]Handling LiveKit Call in Killed State on Android (Flutter WebRTC & JNI Limitations) #843
Description
We’re building a Flutter application using LiveKit for audio/video calls. We understand that the flutter_webrtc plugin relies on Flutter’s JNI bindings, which are terminated when the app is force-closed or in the killed state. Given that, we’re exploring how to handle call-related functionality—such as receiving and responding to incoming calls—even when the app is not running.
Is there currently any supported or recommended approach within LiveKit to manage this use case in Flutter on Android? For example:
Can calls be handled or woken up via FCM or foreground service even when the app is killed?
Or, would we need to offload call handling to native Android code and integrate with LiveKit via the native SDK instead?
We’d appreciate your insights on how to achieve a reliable call experience in such states, and whether Flutter is currently viable for this requirement or if a native implementation is necessary.