Modules report themselves inactive on Vector but activate on LSPosed

[mymine]

Steps to reproduce/复现步骤

On Vector v2.0 (3055-b2dfaacb-dirty) many modules cannot be activated. They activate normally on LSPosed-v2.1.1-7790-release.

The following module cannot be activated at all:

1. Freemoe (me.feimeng.vip)
   https://github.com/Xposed-Modules-Repo/me.feimeng.vip

The following modules only activate once their own package is ticked in their scope:

1. 蓝牙调试 / Bluetooth debugging (net.ankio.bluetooth)
   https://github.com/dreamncn/bluetooth

2. bluetoothhook (com.jingyu233.bluetoothhook)
   https://github.com/jingyu233/bluetoothhook

3. SpoofMyDevice (com.spoofmydevice)
   https://github.com/BuSung-dev/SpoofMyDevice

Expected behaviour/预期行为

The modules activate normally.

Actual behaviour/实际行为

The modules cannot be activated.

Xposed Module List/Xposed 模块列表

net.ankio.bluetooth 93
me.feimeng.vip 101
com.jingyu233.bluetoothhook 93
com.spoofmydevice 82

Root implementation/Root 方案

magisk 30.7.5

System Module List/系统模块列表

ReZygisk v1.0.0 (532-c37ab43-release)
Vector v2.0 (3055-b2dfaacb-dirty)

LSPosed version/LSPosed 版本

Vector v2.0 (3055-b2dfaacb-dirty)

Android version/Android 版本

hyperos3 Android16

Version requirement/版本要求

• I am using the latest debug build from GitHub Actions./我正在使用 GitHub Actions 中最新的调试版本。

Logs/日志

log.zip

[JingMatrix]

It is a regression introduced in my UI rewriting, fixing it now in PR #819.

[JingMatrix]

Thanks for the report and the logs. The three modules that only worked once you ticked them in their own scope are our bug — the Compose manager stopped adding a legacy module to its own scope, which is how such a module detects that it is active. #819 fixes it, and a build is attached to https://github.com/JingMatrix/Vector/actions/runs/30559706716 if you would like to confirm it on your device.

Freemoe is a different matter. I pulled it apart on my own device: it reads getFrameworkName() and, if the answer is not "LSPosed", calls a native method whose only instruction is a write to address zero. That is what the SIGSEGV in your log is — the module deliberately kills the app it was loaded into. We report ourselves as "Vector", so there is nothing to fix on our side; please ask the module author to accept this framework too.