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

[Android] - BackToForeground() sometimes does not work, and call remains in native UI #294

Open
2 tasks done
stephanoparaskeva opened this issue Sep 23, 2020 · 5 comments

Comments

@stephanoparaskeva
Copy link

Bug report

  • I've checked the example to reproduce the issue.

  • Reproduced on:

  • Android

Steps to Reproduce

Call android,
Press Accept on DropDown call UI
UI goes to native incall screen.
BackToForeground() does not return app to foreground

Versions

- Callkeep: latest
- React Native: latest
- Android: 7
- Phone model: Samsung S6
@manuquentin
Copy link
Contributor

Hi @stephanoparaskeva,
please see my comment I think that Samsung have prohibited to display anything abose the native call ui ...

@stephanoparaskeva
Copy link
Author

Hi @stephanoparaskeva,
please see my comment I think that Samsung have prohibited to display anything abose the native call ui ...

Ah it is good news that you are trying to create a workaround so this issue does not remain stagnant!
Thank you :D

@HarshitPadalia
Copy link

Hi @stephanoparaskeva,
please see my comment I think that Samsung have prohibited to display anything abose the native call ui ...

this can be solved if we use self managed connection service? if yes then I can help you for implement self managed connection service

@stephanoparaskeva
Copy link
Author

Hi @stephanoparaskeva,
please see my comment I think that Samsung have prohibited to display anything abose the native call ui ...

this can be solved if we use self managed connection service? if yes then I can help you for implement self managed connection service

What does this mean, what is necessary to do this?

@geraintwhite
Copy link
Contributor

geraintwhite commented Feb 4, 2021

I've noticed that when calling setCurrentCallActive and backToForeground at the same time, there is a race condition where the native UI can remain visible.

My workaround is to put backToForeground in a 0 delay setTimeout after the call to setCurrentCallActive. Not the best solution but it works.

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

4 participants