Sing-box for Android新UI,日志会自动消失
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 4.6k
- Avg merge
- 19d 15h
- Merged PRs (30d)
- 1
Description
Operating system
Android
System version
安卓16
Installation type
sing-box for Android Graphical Client
If you are using a graphical client, please provide the version of the client.
alpha28开始
Version
Description
配置文件中,日志设置为warn,等待出现error报错以后,点开sing-box for android看一下日志,发现此时日志存在。然后把sing-box for android切到后台,过一段时间后再点开sing-box for android,就会发现所有日志都消失了,旧UI则不会出现这个问题。原生安卓,电池已经设置不受限制,应用内已经允许忽略内存限制
Reproduction
这个问题复现非常容易,我可以100%复现。配置文件中,日志设置为warn,等待出现error报错以后,点开sing-box for android看一下日志,发现此时日志存在。然后把sing-box for android切到后台,过一段时间后再点开sing-box for android,就会发现所有日志都消失了,
Logs
日志都消失了,肯定没有日志了
Supporter
- I am a sponsor
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the disappearance in the sing-box for Android new UI: view warn-level logs after an error, background the app, and reopen it after a delay. Compare this behavior with the old UI and confirm that the existing logs remain available after the app resumes; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go
- Domain
- mobile, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100