Skip to content

WaEnhancer Community 0.0.7

Choose a tag to compare

@github-actions github-actions released this 17 Sep 02:08
88534ce

WaEnhancer Community 0.0.7

SHA-256: f009653633a8c8536777c71e278b586eff6015121a0c9ad97372409a2eebce23

Changes since v0.0.6.

What's changed

  • #59 Fix LSPosed module initialization regression from beta 2

Full changelog

This section compiles the descriptions of the pull requests included in this release.

#59 — Fix LSPosed module initialization regression from beta 2

Merged by contribution from @igorcv88.

A/B testing narrowed the total hook-loss regression to v0.0.6-beta-2: v0.0.6-beta-1 loads normally, while beta 2 and the stable 0.0.6 do not appear in LSPosed module logs.

The first change in that interval capable of failing before any WhatsApp hook runs is 59d2ecb (fix: make LSPosed marker best effort). Its initZygote() error paths started reading Utils.DEBUG. Reading that mutable static initializes Utils; Utils has a static Handler constructed from Looper.getMainLooper(), which is application/runtime-oriented state and is unsafe to initialize from the zygote callback. If the optional SystemProperties.set() marker fails on the current Android/LSPosed combination, the error handler can therefore throw while trying to report the optional failure, aborting module initialization before handleLoadPackage().

This patch keeps initZygote() independent of Utils and other app helpers. Marker failures are logged directly through XposedBridge, matching the zygote-safe behavior that existed before beta 2 while preserving the best-effort marker semantics.

Scope is intentionally limited to this regression so device validation can cleanly confirm the cause. The separate stale xposedscope package-name issue is not changed here.