WaEnhancer Community 0.0.15

WaEnhancer Community 0.0.15

SHA-256: 6c7464b03b43bba54688056bf5099d2979f136d246957725766d7953c7495ff9

Changes since v0.0.14.

What's changed

• #83 fix(receipts): find the send job when the hook lands on a helper; log the reply path

Full changelog

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

#83 — fix(receipts): find the send job when the hook lands on a helper; log the reply path

Merged by contribution from @igorcv88.

Context

Follow-up to #82. On a device running #82, the delivered receipt now works: the sender sees two gray ticks. Replies still don't turn the sender's ticks blue, and the module's red indicator on incoming bubbles never turns green. So the reply path never reaches the release with matching hidden rows. The symptom predates #65/#66, so the outgoing lookup that #82 removed was not the only cause.

Changes (SeenTick)

• Job discovery. The hook is placed by the log string SendE2EMessageJob/onRun. If that method is declared on a helper or lambda class, isInstance(thisObject) was false on every send and the hook returned silently. findSendJob now takes the job from the hooked instance, an argument, or an instance field of the helper.
• Release key. Hidden rows are keyed by PN. chatReleaseJid uses the job JID if it has a PN form, else the outgoing message's own key, else the open conversation when it is the destination.
• Diagnostics. At install, a WaEnhancerX/Receipts log line records where the hook landed (declaredOnJob). Every skip and failure is logged, and hook exceptions are caught.

Validation

git diff --check passed. This is not compiled: there is no Android SDK in the authoring container. No device run, no workflow dispatched. This is a hypothesis-driven fix plus diagnostics. The log from the next device run decides which case applies; handoff.md lists how to read it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GZkiCkRpn2AMgL42r8yKC8

---

Generated by Claude Code