signalapp / signalapp/Signal-Android

archive chat conflicts with multitasking gestures

Open
#11,461 12 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description


Bug description

When an android device uses navigation gestures instead of the 'old-school'-navigation bar, moving back to the last app (swiping right at the bottom of the screen) archives the last visible chat.

Steps to reproduce
  • Go to chat overview
  • swipe right at the bottom of the screen to go to the last app
  • see a slight green shimmer before the app switches
  • go back to signal, see that the chat has been archived

it should be mentioned that the result of point 4 is not consistent. Sometimes, depending on how fast the user swiped it can be reproducible, but often it does not finish archiving the chat.

Actual result: Sometimes the chat gets archived
Expected result: When a user switches the app, chats should never be archived.

Maybe the archive function should be on a timer that unarchives the chat if the app does get dismissed in a (very)short time, i think disabling the swipe action for the last visible item is not actually doable or reasonable.

This is the same underlying issue as in #10894

Device info

Android version: 11
Signal version: 5.15.6

Link to debug log

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 gesture conflict on Android 11 with Signal 5.15.6 using the listed steps, then compare the behavior with the underlying issue in #10894. Done means switching apps with the bottom swipe never archives the visible chat, including during rapid or interrupted swipes.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.