[Bug] 9.0.0下回复自动去除@重启后失效
- Dominant language
- Java
- Stars
- 5.7k
- Forks
- 416
- Avg merge
- 10d 4h
- Merged PRs (30d)
- 4
Description
### 复现步骤 / Steps to reproduce
1. 启用"禁止回复自动at"
2. 测试,正常去除
3. 重新启动qq
4. 功能失效,且显示依赖异常
### 预期行为 / Expected behaviour
回复去除at功能持久化生效
### 实际行为 / Actual behaviour
初始化未报错,但仅在当前会话中正常生效,qq被后台关闭或重载后失效,且功能异常列表中显示为依赖错误,初始化的两个变量变为false
### 你使用的Xposed框架 / Xposed Framework you used
LSPatch
### 你使用的安卓系统版本 / Your Android version
Android 16
### QQ(TIM) 版本 / QQ(TIM) Version
qq 9.0.0.14110
### 模块版本 / Module Version
1.6.0.r2908.2c00c45
### 版本和其他要求 / Version and Other Requirements
- [x] 我正在使用最新 CI 调试版本且启用详细日志 / I am using latest debug CI version of QAuxiliary and enable verbose log
- [x] 我使用的 QQ 是官方发布的正式版本,而非修改版或测试版 / The QQ I am using is an official release version, not a modified or beta version
- [x] 我已经在 [Issue Tracker](https://github.com/cinit/QAuxiliary/issues) 中找过我要提出的问题,没有找到相同问题。重复问题会被关闭。
- [x] 我已知晓并同意,此处仅用于汇报主程序中存在的问题。若这个 Issue 是关于其他非程序本身问题,则我的 Issue 可能会被无条件自动关闭或/并锁定。
- [x] 我已知晓并同意,如果我不按照模板提供的指示进行填写,则我的 Issue 可能会被无条件删除。
### 日志 / Logs
1.6.0.r2908.2c00c45
QQ9.0.0(5282)
PID: 730, UID: 10705
cc.ioctl.hook.ui.chat.ReplyNoAtHook
isInitialized: false
isInitializationSuccessful: false
isEnabled: true
isAvailable: true
isPreparationRequired: true
errors: 0
--------------------
1.6.0.r2908.2c00c45
QQ9.0.0(5282)
PID: 730, UID: 10705
cc.ioctl.hook.ui.chat.ReplyNoAtHook
isInitialized: true
isInitializationSuccessful: true
isEnabled: true
isAvailable: true
isPreparationRequired: true
errors: 0
### 补充说明(可选) / Additional information (optional)
_No response_
Contributor guide
Research direction
Start with the ReplyNoAtHook entry point named in the logs and inspect how its initialization state and settings behave across a QQ restart. Reproduce on LSPatch with Android 16 and QQ 9.0.0.14110, then verify that removing @ from replies remains enabled after reload and that no dependency error is reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100