handleLoadPackage() not called for app using appComponentFactory #513
Unanswered
agnostic-apollo
asked this question in
Q&A
Replies: 4 comments 2 replies
-
|
There seems to be error is you LSPosed logs, please upload the complete logs of debug build. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I was using release build before, I didn't know it didn't have debug info with verbose logs enabled. Following is the log after hooked app is started, I cleared the log before I started it. Hopefully that's enough, if you need logs from earlier in the boot, let me know. Note that |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
You surely cannot hook any method you want in an Android application. Instead, you should analyze the correct execution flow of the target app and set up the hooking points properly. This is not a problem of LSPosed, it is your task while designing a module. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I cannot hook methods if I looked more into the issue. Following is the normal stack and logs for the hooked app if it does not specify Following is the stack and logs for the hooked app if it does specify The issue is that if the app specifies an app component factory, then it can add app specific code to package androidx.core.app;
public class CoreComponentFactory extends android.app.AppComponentFactory {
static {
// `<clinit>`: App specific code.
}
}The
The
Previously,
Additionally, note that there are 2 class loaders maintained for the app by the framework, the
LSPosed could add a I think for a solution to be implemented, another interface like A module setting could have been added in module resources for where it can define list of packages for which If you have any better ideas, feel free to suggest. I haven't looked too deeply so may be missing something too. |
Beta Was this translation helpful? Give feedback.
-
|
That is an interesting proposal, I will consider it once the refactoring of LSPosed is done. Personally, I don't think hiding root via LSPosed could help, it is usually better to write zygsik modules directly. Alternative, try maybe this one: https://github.com/Mrack/TInjector_Symbi |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
That would be great, thanks. I will try looking into testing my design when I get time, busy with termux rewrite work myself. If you override the methods used for root checks in the app itself, then it can work, I have already done it with apktool decompile/recompile for many apps, but APK sources don't always recompile due to apktool/resource issues, doesn't work for native checks, and requires changing signing keys, which apps often have additional checks for. So LSPosed way would be easier, especially with hooked app upgrades, as only obfuscated class/function names would need changing in module. Trying to hide root with modules and root solutions has become a cat and mouse game and lot of the solutions are closed source, LSPosed would be easier for personal use case. Thanks, I will look into it. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Steps to reproduce/复现步骤
AndroidManifestApplication_appComponentFactory, like forandroidx.core.app.CoreComponentFactory.Expected behaviour/预期行为
handleLoadPackage()gets called.Actual behaviour/实际行为
handleLoadPackage()not called beforeappComponentFactoryclass of the app is loaded, so methods cannot be hooked. Is hooking methods supported so early on?Xposed Module List/Xposed 模块列表
Root implementation/Root 方案
Magisk 29
System Module List/系统模块列表
LSPosed version/LSPosed 版本
v1.10.2 (7199) 0e457e3
Android version/Android 版本
.
Version requirement/版本要求
Logs/日志
Stacktrace without xposed module.
Stacktrace with xposed module.
Logcat logs. Note sure which elf is triggering
Compressed data is corrupterror or why.Beta Was this translation helpful? Give feedback.
All reactions