[Feature Request] Implement "Invalidate inline hooks" to bypass detection points
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- mobile-dev, security
Research direction
No source files or tests are named. Start by reviewing Vector's settings implementation and the linked pull request #921, then compare the requested behavior with the official LSPosed manager's "Invalidate inline hooks" feature. Done means the feature is available in Vector settings and allows affected targeted apps to launch without the reported force close.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?/你的请求是否与某个问题相关？
Yes. When I use a module (requiring API 100) and target a specific app (e.g., HungerStation), the app immediately force closes upon launch. In the official LSPosed manager, this specific crash can be bypassed using the "Invalidate inline hooks" feature. Since Vector currently lacks this feature, the app remains completely inaccessible when targeted by the module.
Describe the solution you'd like/描述你想要的解决方案
I would like to request the implementation of the "Invalidate inline hooks" (Cleanup libart.so for listed apps) feature in Vector's settings, similar to how it exists in the official LSPosed manager. This would serve as a necessary workaround to allow stubborn apps to launch successfully when targeted.
Additional context/其他信息
Device: Tecno Camon 30 (Model: CL6)
Vector Version: 2.0 (3021)
Note to developer: As requested, I am attaching the crash logs to this issue to demonstrate the force close that occurs due to the absence of this feature.
- Dominant language
- Kotlin
- Stars
- 12.6k
- Forks
- 850
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from JingMatrix/Vector
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
JingMatrix/Vector#999 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
JingMatrix/Vector#997 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JingMatrix/Vector#996 ·
Maintainers usually reply within 1 day
-
Modules not visibleOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
JingMatrix/Vector#991 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JingMatrix/Vector#990 · 1 comment ·
Maintainers usually reply within 1 day
All issues in JingMatrix/Vector
Similar issues
-
Source: c7 Type: bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
navikt/esyfo-narmesteleder#654 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nonbili/meron#79 · 1 comment ·
Maintainers usually reply within 1 day
-
Source is down
Difficulty 1/5 Under an hour Newbie friendliness 70/100
keiyoushi/extensions-source#19728 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vaadin/intellij-plugin#601 ·