Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strip most logs in the release version #101

Merged
merged 3 commits into from
Nov 25, 2024
Merged

Strip most logs in the release version #101

merged 3 commits into from
Nov 25, 2024

Conversation

JingMatrix
Copy link
Owner

@JingMatrix JingMatrix commented Nov 25, 2024

Given that it is not easy for module developers to hide logs of LSPosed from apps, I am stripping logs from LSPosed in the release version.

Please leave your comments here on this decision.

Technical details:

  1. The log function in LSPosed can be toggled using the static field beSilent of class org.lsposed.lspd.util.Utils.Log.
  2. Developers are encouraged to use the debug version of LSPosed to develop modules.
  3. Logs using Xposed API XposedBridge.log and any error logs aren't and will never be stripped

In the release version, we remove some logs (except error level) added into the injected process.
This helps to leave fewer unnecessary logs which are impossible for modules to hide.

This function can be toggled using the static field `beSilent`.
Developers are encouraged to use the debug version of LSPosed to develop modules.
@Stillhard
Copy link

Can't express enough ❤️

We use the verbose log toggle to control if logs are stripped
@JingMatrix
Copy link
Owner Author

Instead of alway stripping logs in the release version, now users can control it from the manager Disable verbose logs

@JingMatrix JingMatrix merged commit 466b3a4 into master Nov 25, 2024
1 check passed
@JingMatrix JingMatrix deleted the strip_log branch December 9, 2024 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants