A certain module is crashing an app #7
Comments
Rtizer-9
changed the title
|
Some info that might be helpful for you: I've frequently faced this app crash error with android faker, geergit and ssl-killer modules with instagram or whatever is under scope with almost all releases of mywalkb. The pumpcin fork worked perfectly with all these modules except the last release which was incompatible with waenhancer. I'm telling you this because I think all these problems are linked to a common thing for which pumpcin already had patched his fork. PS: Thanks for picking up the development of LSPosed, really appreciate it. |
|
On Android Faker, there is an option to fake the device (model name and Android version). From Android 14, it is necessary to specify RECEIVER_EXPORT or RECEIVER_NOT_EXPORT. If Android Faker is faking for a version lower than 14 and the App's target SDK (Instagram) is 14, it will throw this exception. |
|
more info here |
|
@Dev4Mod Working after turning off that option. Should I close the issue now. From what I understand lsposed can't/shouldn't do anything about and android faker itself should have prop available for a14 first (I checked it only has a13 and below). |
JingMatrix
added
question
|
@JingMatrix ssl killer module is still crashing. |
Please provide some necessary logs. It is not an open source App, which further requires root permission to run. |
|
I know the Dev of this module, apparently it seems to be a problem in a hook of the module. But I did a shallow investigation, but this is not a problem of LSPosed. Besides, there's a strange lib on Instagram "libaborthooks.so" this might be a protection for hooks, I'm not sure. But I repeat, it's not a problem of LSPosed. |
|
@JingMatrix fyi, the latest build in actions allows usage of ssl killer without any app crash. It's a different thing if it works on an application or not, and whether it's completely crashing the app. The latest build doesn't crash the apps outright on launch. |
|
This is the crash log. |
|
@JingMatrix can you please check if corepatch is working for you on latest action build. |
Surely working, I am using it daily. Please also provide the build's link you would like to refer to, in case you meant another one. |
|
I installed the latest action build of both of your lsposed and core patch and it's not working. Earlier I was obviously using the official one provided in the lsposed repo itself. LSPosed_2024-09-02T12_38_18.846840.zip |
|
I installed another lsposed fork (lsposed npm) and on that it works. |
Try using this with no LSPlant update like in npm-open: |
|
@Rtizer-9 Did you disable logs in the LSPosed settings ? By the way, is there a version of LSPosed or/and CorePatch that once worked for you? |
Disabling logs functionality was only present in pumpcin fork and the now active lsposed-npm and afaik your fork can only disable verbose logs not normal logs (sorry if I remember incorrectly).
I'll keep that in mind from now on.
Version of your fork or others? In others, no other fork/version ever gave this problem so it's just some temporary error introduced in one of your action build. I only needed that functionality right now so I don't remember which earlier version was working. Except this time I've never installed a fork of corepatch. And as I mentioned npm fork latest build is working (they've some huge patches from your builds as they give credit in every release). |
|
Update: I tried both latest action build from master branch as well as the build suggested by @Stillhard but both do not work. |
Could you please provide logs for this test? |
|
I disabled zygisk-next > got some errors in other modules > installed them again but shamiko 357 clearly says unsupported environment. I took the logs though on latest master branch build Aren't the devs of shamiko same as the devs of magisk alpha then how come shamiko isn't compatible with alpha inbuilt zygisk? The reason I use zygisk-next is because of it's great changelogs describing how compatible and more undetectable it becomes release by release. I've also installed rezygisk but shamiko release after a certain version is completely incompatible with it according to its dev. All my modules are working fine so which module is causing errors with zygisk-next? I can see iamnotdeveloper not playing great with whatsapp but that's probably because whatsapp do not need it at all I guess. PS: These Lsposed npm guys seems to be doing some interesting work here https://t.me/rormzhstjxm and their fork is making lots of noises in communities probably because of being more undetectable probably solely because of that mywalkb patch of disabling watchdog log which you already seem to be implementing in your own fork. At the moment it seems like they've just merged different patches from devs who have already commited to your repo. |
|
@Rtizer-9 From your logs, there is always this line: And then LSPosed stops to work, the log also ends. For your P.S, my passion concentrates on open source world. My pleasure comes from my contributions to the project, and I don't care that much of fame or others' behaviors. For people who are involving in this community, I suppose they know how to appriciate and respect open source projects properly. Their engagements and aesthetic tastes motivate me to maintian this repo. |
|
I completely agree with and understand everything you said above. The reason I'm using this setup is only because of its stability and best root detection bypass and nothing else. A normal user only cares about that irrespective of how big the error log becomes because all the apps/modules are working fine for me. For the npm thing if you look at my comment edit history, I'd actually written for you to collaborate with these guys but from what it looks like they've just merged the hiding patches and that new parasitic manager so obviously you're the guy doing main development so it's stupid to ask you to take some "inspiration" from them and that's why I deleted that. So that's all I meant by mentioning their fork. I guess I'll trouble you the day about that core patch issue when I'll be left with no choice because I can't lose the root detection bypass alpha and shamiko provides because my bank apps do need that. As I already mentioned I did try to do what you suggested but shamiko is incompatible (even to me it's surprising) so I'm left with no choice other than use zygisk-next and alpha. Thanks for assisting. I'll keep testing your latest builds meanwhile 👍 |
|
@Rtizer-9 Did you use the debug version of LSPosed when you sent the logs? If not, please do it. |
|
I installed both the latest debug build of corepatch and lsposed and phone is stuck on boot; it's not a bootloop but it's just stuck there. I'll update if I manage to boot or if you've some advice to make it boot then I'm all ears. Update: No luck, it won't boot. |
Okay, next time, do use the debug version. As you have said in the issue, , otherwise it was wasting my time since I supposed that you already knew it.
If you cannot boot your phone at all, try enter the safe mode. For debugging the issue, I need logs for that, you may try run the following command from a computer since the moment that your screen is on: I guess there were conflicts between modules. |
|
Sure. I recovered the phone and booted somehow and will update with debug logs if I manage to boot it in debug when I get some time. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I am now using the debug version of the core path |
|
@Nimpip Core Patch seems working well on your device, which functions of it doesn't work as expected ? |
Applications with different signatures cannot be overwritten |
|
And when I used the core of the Lucky cracker to crack the magik module, the function worked, so I guess it's not a problem with my system |
build(fix): patch wrong build configurations of submodule `fmt`
Steps to reproduce/复现步骤
Expected behaviour/预期行为
Actual behaviour/实际行为
Xposed Module List/Xposed 模块列表
Magisk Module List/Magisk 模块列表
LSPosed version/LSPosed 版本
1.10.0 (7082)
Android version/Android 版本
14
Magisk version/Magisk 版本
Magisk alpha 27006
Riru version/Riru 版本
N/A
Version requirement/版本要求
Logs/日志
LSPosed_2024-08-29T19_35_47.817727.zip
LSPosed_2024-08-29T19_35_52.300657.zip
The text was updated successfully, but these errors were encountered: