iOS swipe back navigation gesture does not work if Signal was opened from a notification

Open
#5,853 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the notification-open flow on iOS: close Signal, open a chat from a notification, and test the edge-swipe back gesture before and after reopening the chat from the back button. Trace the notification entry path and navigation gesture handling; done means the gesture returns to the chats list immediately after opening from a notification.

Written by the indexing model from the issue text.

Description

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

Describe here the issue that you are experiencing.

On iOS, when a Signal notification for a chat is opened, Signal will open to the chat. It is not possible to use the universal gesture for navigating back on iOS. Typically, when you place your finger on the left edge of the screen and swipe right, the application will go back to the previous menu. Instead, you need to click the back arrow which makes for a clunky experience.

Steps to reproduce
  • Close the Signal app
  • Open a Signal notification
  • Use the iOS back gesture as described above to navigate back
    • Note that the gesture fails
  • Click the back button
  • Click the chat again to re-open it
  • Try the back gesture
    • Note that it works now

Actual result: The gesture does not work as intended leading to a non-uniform and clunky iOS experience

Expected result: The gesture should allow the user to seamlessly and elegantly navigate back to the chats list

Screenshots

N/A

Device info

Device: iPhone 7

iOS version: 15.8.2

Signal version: 7.23 (258)

Link to debug log

link

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

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.

More from signalapp/Signal-iOS

All issues in signalapp/Signal-iOS

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.