Rejoining a VC ignores your mute/deafen preference in a certain scenario

(#2116) Bug Fixed mobile voice

Observed behaviour

When rejoining a voice channel where you were mute/deafened, the app remembers your preference and rejoins as mute and deafened, instead of using the default shown in the join vc modal (which is unmute and undeafened). This does not occur in the opposite direction. Remembering the user's last deafen/mute status is good, but if you are going to do this it must be reflected in that modal shown to the user before joining, and whatever is configured there should be respected to avoid an unintended setting (whether that's hot mic or accidental mute).

Reproduction steps

  1. Close and reopen the app just to get a clean slate
  2. Connect to a voice channel
  3. Tap the Deafen button to both mute and deafen
  4. Disconnect
  5. Tap a random text channel
  6. Tap the voice channel again
  7. Note that as you connect, you have not selected Mute or Deafen
  8. Connect to voice

Build information

Version 1.0.0, Beta 57, Channel Beta, Build 2366, Android 16 (arm64), Device Google Pixel 9a, Locale en-US, Push fcm, Flutter 3.47.1, Dart 3.13.1

Platform

Android

Evidence

Video demonstrating the behavior

Details

Expected behaviour The mute/deafen preference should follow whatever is in the last modal before joining. Since the voice call join modal defaults to unmuted and undeafened, I would expect to join any call unmuted and undeafened, regardless of my previous join settings.
video.mp4 | 993 kB
  1. Rex changed the status from Needs triage to Fixed

2 comments

Sign in with Fluxer to comment and vote.
Comment by bizo
bizoReviewer 1 vote
Can reproduce CR - Version 1.0.0, Beta 58, Channel Beta, Build 65, iOS 26.6 (arm64), Device iPhone13,1, Locale en-GB, Push apns, Flutter 3.47.2, Dart 3.13.2
Comment by mesub
mesubMod 1 vote
Can reproduce CR: Version 1.0.0, Channel Canary, Build 2388, Android 15 (arm64), Device OnePlus CPH2465, Locale en-GB, Push fcm, Flutter 3.47.2, Dart 3.13.2