signalapp / signalapp/Signal-iOS

Playing forwarded voice messages will autoplay the next voice message from the wrong chat

Open
#6,339 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
12.2k
Forks
3.5k
PR merge metrics
No merged PRs in 30d

Description

  • I have searched open and closed issues for duplicates
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic

Bug description

After forwarding a voice message from chat A to chat B and playing the message in chat B, the next voice message from chat A will autoplay.

Steps to reproduce
  • Record two voice messages in chat A.
  • Forward the fist voice message to chat B.
  • Play the voice message in chat B.

Actual result: After the first voice message plays, the second voice message in chat B will autoplay.

Expected result: No second voice message should play.

Note: If you create another voice message in chat B after forwarding, the correct behaviour (plays the second message in chat B) will occur.

Device info

Device: iPhone 16

iOS version: 26.6.1

Signal version: 8.26 (1826)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the issue on iOS by recording two voice messages in chat A, forwarding the first to chat B, and playing it there; start by tracing forwarded voice-message playback and the next-message selection. Done means the second message from chat A does not autoplay, while the expected behavior for messages created in chat B remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.