Call Decline Not Triggering After First Call Accept in Flutter App (Old Implementation)

[keshav-sf]

I am experiencing an issue in my Flutter app using the GetStream SDK where the decline functionality doesn't work after the first call is accepted. The issue specifically occurs when the first call is accepted and then ended, after which the second call’s decline action fails to trigger. It seems the decline function is not executed at all after the first call ends.

Steps to Reproduce:

1. Accept the first incoming call in the Flutter app.
2. End the first call.
3. When the second incoming call arrives, attempt to decline it.
4. The decline function does not execute, and nothing happens.

Expected Behavior:

The decline function should work as expected after the first call ends, allowing the user to decline the second incoming call.

Actual Behavior:

After accepting and ending the first call, the decline action for the second call fails to trigger, and the function isn't executed at all.

Environment:

• Flutter Version: 3.27.3
• GetStream SDK Version: [Insert GetStream SDK version here]
• iOS Version: 17.7.2 and 18.0.1
• Device: iPhone 13 & 15

Code Snippet (Old Implementation):

callKitEventSubscriptions.addAll([
    streamVideo.onCallKitEvent<ActionCallAccept>(_onCallAccept),
    streamVideo.onCallKitEvent<ActionCallDecline>(_onCallDecline),
    streamVideo.onCallKitEvent<ActionCallEnded>(_onCallEnded),
    streamVideo.onCallKitEvent<ActionCallToggleMute>(_onCallMute),
    // Additional event handlers if needed
]);

Additional Notes:

• This issue only happens on iOS.
• I am using the old implementation of CallKit event handling because certain features like custom data are not working correctly with the new implementation.
• Could you investigate why the decline function isn't being triggered after the first call ends?

Possible Solution / Further Investigation:

I would appreciate if you could look into the iOS-specific behavior that causes the decline function to fail after the first call is accepted and ended. If any changes are needed in the code or configuration, please let me know.

[keshav-sf]

@Brazol or @deven98 Were you able to reproduce the issue, or do you need more information?

[Brazol]

Hey @keshav-sf, we couldn't reproduce the issue. If you haven't already, please review our updated documentation on incoming calls to ensure your integration is set up correctly. We've also created a tutorial that will help you check the integration step-by-step.

If the problem still persists, please try to reproduce it on our ringing tutorial app and feel free to reopen this issue. Thank you!