Skip to content

Conversation

@WofWca
Copy link
Member

@WofWca WofWca commented Jan 25, 2026

Related:

I have tested this, but I did not test the caller not enabling video (I don't have a version that supports this).

Copy link
Member

@nicodh nicodh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed by testing & reading

I tested with 2 instances running on desktop. I con confirm that if the caller disables video immediately after calling the receiver has no video option at all.

@WofWca
Copy link
Member Author

WofWca commented Jan 26, 2026

I con confirm that if the caller disables video immediately after calling the receiver has no video option at all.

Ummm that is not supposed to happen. Are you using Core 2.39.0?

@nicodh
Copy link
Member

nicodh commented Jan 28, 2026

I con confirm that if the caller disables video immediately after calling the receiver has no video option at all.

Ummm that is not supposed to happen. Are you using Core 2.39.0?

Yes but the reason was that the camera can only be assigned to one instance so it was not related.

So what exactly is the expected behaviour? According to the title I expected that if the caller disables video the receiver should just receive an audio call.

@WofWca
Copy link
Member Author

WofWca commented Jan 28, 2026

The caller has to specify that they did not enable video by providing a boolean to the "Start Call" Core function. Which only the new iOS PR does currently.
Desktop doesn't yet have the button to start an audio-only call.

I guess we could check if the camera is enabled when the call is started, for example, to handle the case where the device doesn't have camera at all, but I suggest to do it in a future MR.

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

Successfully merging this pull request may close these issues.

3 participants