Callkeep minimised in the top left corner?

[dackom]

Bug report

• [X] I've checked the example to reproduce the issue.

• Reproduced on:

• [ ] Android

• [X] iOS

Description

Sometimes, after playing a lot with starting ending calls... I am getting "minimised" phone icon in the top left corner, which I cannot open, tap, or anything else... it is just "ringing" there, but I cannot interact with it. Doesn't matter if app is running, or if it's killed, only thing that helps is restarting the phone.

Steps to Reproduce

I am not really sure. Usually everything works ok, but sometimes this happens.

Versions

- Callkeep: 4.3.1
- React Native: 0.64.2
- iOS:15, 15.1, 15.2
- Android:
- Phone model:  iPhone X, iPhone 13 pro

Any ideas?

[CMLCNL]

same issue. i dont know what is this. sometimes call ringing stuck top left corner. when i reboot phone its work normally again.

[swcloud1]

I also have the same issue and I cant find any information. After the call icon is stuck in the left corner the only way to reset it seems to be to call my device from a different device. After this the call comes in normally before it gets stuck in the top left again and becomes unclickable.

[CMLCNL]

I also have the same issue and I cant find any information. After the call icon is stuck in the left corner the only way to reset it seems to be to call my device from a different device. After this the call comes in normally before it gets stuck in the top left again and becomes unclickable.

I have never come across a production.

[swcloud1]

I also have the same issue and I cant find any information. After the call icon is stuck in the left corner the only way to reset it seems to be to call my device from a different device. After this the call comes in normally before it gets stuck in the top left again and becomes unclickable.

I figured it out. The trick was to change the UUID after a failed call. I dont think this should be necessary but it works.

[jonastelzio]

This happens because there's a call "stuck" in CallKit. It's probably because of a failure, and reportCallEnded (or whatever the method name is), wasn't called appropriate - so CallKit (and CallKeep) has no idea you're not actually servicing this call.

I figured it out. The trick was to change the UUID after a failed call. I dont think this should be necessary but it works.

You shouldn't be reusing UUIDs between calls ;)