signalapp / signalapp/Signal-Android

Recipient search text is not selected after choosing a contact in multi-recipient picker

Open Beginner friendly
#14,908 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
29.4k
Forks
6.9k
PR merge metrics
No merged PRs in 30d

Description

Guidelines
  • 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

In multi-recipient flows such as forwarding messages, after selecting a recipient from the search results, the current search text remains in the recipient search field but is not selected.

Because of that, searching for the next recipient requires an extra manual step each time: clearing the field, backspacing the old query, or manually selecting the text before typing again.

This makes repeated recipient selection slower than expected in flows that stay open after each selection.

Steps to reproduce
  1. Open a multi-recipient flow such as message forwarding.
  2. Type part of a recipient name in the search field, for example Ali.
  3. Select that recipient.
  4. Immediately try to type the next recipient’s name.
Actual result

The previous query remains in the field and is not selected, so the next input appends to it or requires manual clearing/replacement.

Expected result

After a recipient is selected, the existing search text should remain visible but be fully selected, so the next keystroke replaces it immediately.

Additional context

This appears most relevant in multi-recipient flows that stay open after each selection. Single-select flows that immediately navigate away are not materially affected.

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

Start by reproducing the multi-recipient forwarding flow and tracing the recipient search field after a contact is selected. Done means the existing query remains visible and is fully selected so the next keystroke replaces it; verify that single-select flows are not materially affected.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
67/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.