import{_ as a,r as n,o as s,c as i,b as o,d,a as t,e}from"./app.7900f22c.js";const c={},u=t('
The future is bright and uncertain, let us look forward to the future development space of
YukiHookAPI
.
Here are the unresolved issues with
YukiHookAPI
.
Currently only supports LSPosed perfectly, other Xposed Framework need to downgrade the module target api.
TaiChi may not be supported at all, and TaiChi needs a lower target api to adapt on high-version systems.
Some Xposed Module developers currently choose the Hook target app self's SharedPreferences storage solution to solve the module settings sharing problem.
In the later period, the permissions of the Android system will become more and more strict, and selinux
is a big problem currently facing, which needs to be discussed and studied.
Features that
YukiHookAPI
may add later are included here.
If you like the Reflection API of YukiHookAPI
, but your project may not need related Hook functions.
Well here is some good news for you:
',14),l=e("The core Reflection API of "),h=o("code",null,"YukiHookAPI",-1),p=e(" has been decoupled into "),f={href:"https://github.com/fankes/YukiReflection",target:"_blank",rel:"noopener noreferrer"},m=e("YukiReflection"),k=e(" project, which can now be used in any Android project."),b=t('To be Discussed
At present, the API only supports binding to xposed_init through the automatic builder.
If you don't like the automatic builder, you must implement the module loading entry yourself.
In the future, the Lite version with only API functions will be launched according to the number of people required.
You can submit issues with us.
We have provided the Xposed native API listening interface, you can find or view the implementation method of the Demo here.
As an API, currently only docking XposedBridge
as a compatibility layer still has certain limitations.
Most inline hook
do not have a Java
compatibility layer, and the Java
compatibility layer adaptation of native hook
may be considered later.