Call cannot be accepted when recording consent is needed.

[ArminXG]

Steps to reproduce

1. Setup conversation with possible recording and required consent
2. Call user who uses iOS Talk App
3. Called user cannot accept the call

Expected behaviour

The iOS user should be able to "consent" and accept the call.

Actual behaviour

iOS Talk App just gives the error that call cannot be accepted because of missing consent (without asking for consent). Starting a call is without problem, here the user is asked for consent.

Device information

Device: iPhone 16e

iOS version: 26.6.1

Talk version: 24.0.4

Server information

Nextcloud version: 34.0.3

Talk version: 24.0.4

Custom Signaling server configured: yes, 2.1.1 docker

Custom TURN server configured: yes

Custom STUN server configured: yes

[SystemKeeper]

Thanks for raising this issue. This is currently by design and working as intended. If the call comes in through CallKit, we don't have an option to ask for consent. We don't even have the option to open the app directly, if I remember correctly. So we could probably show a local notification with two buttons to consent, but not sure that is working reliable.
Maybe we can investigate it at some point, for now this is how it is designed.

[ArminXG]

It is intended? But the user cannot accept a call then. Or how should the app be used to accept a call when consent for possible recording is needed?

[SystemKeeper]

The user can join the call from the app, then the consent dialog will be shown and can be accepted.

[ArminXG]

You mean the user shall ignore/decline the incoming call, change to the list of conversations, find the correct one and join here?
Seriously? The users will not do that, to complicated.
Isn't it possible to add the consent somewhere else? I am wondering, it works on Android perfectly.

[SystemKeeper]

Well, yea I can see it is not ideal, at the same time (as said and if I remember correctly), there's no way to force us to show the app on an incoming call. Still we are forced to show an incoming call screen from CallKit (that's a requirement by iOS). So there's no way for us to reliable show the consent dialog. Also there would be an issue if someone accepts the call via bluetooth for example.

As said above, we might revisit the topic, but for now, that's how it was designed/implemented back then.