SagerNet / SagerNet/sing-box

Android back gesture from connection details returns to Dashboard instead of Connections list

Open
#4,057 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
38.1k
Forks
4.6k
Avg merge
19d 15h
Merged PRs (30d)
1

Description

Operating system

Android

System version

10

Installation type

sing-box for Android Graphical Client

If you are using a graphical client, please provide the version of the client.

1.13.8

Version

Description

When viewing a connection’s details, using the Android system back button/gesture jumps back to the Dashboard instead of returning to the Connections list, while the in-app back button behaves correctly.

Reproduction
  1. Open sing-box for Android.
  2. Go to a profile’s Connections list.
  3. Tap any connection to open its Connection Details screen.
  4. Use the Android system back button/gesture to go back.

Expected behavior

System back button/gesture should return to the Connections list for that profile (same as the in-app back button in the top-left).


Actual behavior

System back button/gesture sends the user all the way back to the Dashboard, skipping the Connections list.
The in-app GUI back button in the top-left works correctly and returns to the Connections list.

Logs

Supporter
Integrity requirements
  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Contributor guide

No contributing guide indexed for this repository

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 file or test is named in the report. Reproduce the path from a profile's Connections list to Connection Details, compare the Android system back gesture with the in-app back button, and trace the Android client's navigation handling. Done means system back returns to the Connections list on Android 10, matching the in-app button.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.