Skip to content

Native Incoming call issue #517

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

Open
dsonigara opened this issue Jan 27, 2025 · 2 comments
Open

Native Incoming call issue #517

dsonigara opened this issue Jan 27, 2025 · 2 comments
Labels
Out of scope The problem described isnt an issue with this package, its likely something else in their setup

Comments

@dsonigara
Copy link

Android:
On Android, the default incoming call screen appears as expected. However:

When I click on "Accept Call," the call is accepted, but a second screen opens in the background instead of displaying the default call screen after the call is accepted.
I would also like to handle the native Android hangup event.

iOS:
On iOS, the call functionality works fine while the app is in the foreground. However, when the app is in the background, the call notification appears, but when I click on "Accept," the call immediately hangs up.

Any guidance on these issues would be greatly appreciated!

@nikhilingle1302
Copy link

@dsonigara I'm also having some problem with the calling, could you please help me with that?

@mikaelwills
Copy link
Collaborator

@dsonigara when you're refering to notifications are you talking about callKit UI in iOS and the Android equivalent?
The functionality you're talking about is possibly outside the scope of this package, and more in the scope of the callKeep package.
Also provide some sort of logging so we can see why iut immediately hangs up.

@mikaelwills mikaelwills added the Out of scope The problem described isnt an issue with this package, its likely something else in their setup label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Out of scope The problem described isnt an issue with this package, its likely something else in their setup
Projects
None yet
Development

No branches or pull requests

3 participants