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

findcall is not working #438

Open
Kumargaurav11998 opened this issue May 10, 2024 · 8 comments
Open

findcall is not working #438

Kumargaurav11998 opened this issue May 10, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@Kumargaurav11998
Copy link

Describe the bug

when i get notification in background then after register , i am trying to find call using call id but i am getting null
Screenshot 2024-05-10 at 2 01 15 PM

how i can i fix ? please help ?

@Kumargaurav11998 Kumargaurav11998 added the bug Something isn't working label May 10, 2024
@eduardothiesen
Copy link

I am facing this issue as well

@victortive
Copy link
Contributor

The plugin won't save the call information if the app is killed and the plugin isn't set up. You can either initialize and register in the background or save the call information so the app can read it once it is in the foreground again.

@eduardothiesen
Copy link

@victortive do you have any suggestions on how to use the saved call? Because in the cases the call arrives after a notification in killed state, the SipUaHelper instance is not the same on the background isolate and main isolate

@victortive
Copy link
Contributor

if the SipUaHelper is not the same instance consider wrapping it in a class and making that class a singleton

@eduardothiesen
Copy link

eduardothiesen commented Aug 6, 2024 via email

@victortive
Copy link
Contributor

try saving it in shared preferences on the native side and reading it on the dart side

@eduardothiesen
Copy link

I don't know if that would work. Since shared preferences only accepts serializable types and also if I save let's say, the informations of the call, I think it's not possible to attribute the saved call to the new instance SipUaHelper

@Vinayak0-0
Copy link

One way to work it out is, keeping the SIPUAHelper in background isolate and sending only the neccessary information to the main isolate.

In your case, send the call ID to background isolate, find the Call, handle it there and send those UI related infos to main isolate like for showing active call or any as you prefer.

But one constraint here is the video call implementation. As we need to pass MediaStream to main isolate and we can't serialize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants