Conversation
WppCore.sendMessage targeted an ActionUser method whose shape no longer exists on WhatsApp 2.26.x, so sending silently did nothing (this also broke the Tasker "send message" integration). Instead, resolve the current text-message sending facade: - the facade class is found dynamically by its marker string, - the send method by its (Jid, String) -> void signature, - the instance is captured from the facade constructor, all via the existing Unobfuscator/DexKit convention, with a legacy ActionUser fallback for older versions. Sending now also runs on the main thread and reports failures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
WppCore.sendMessage looked for an ActionUser method with the shape
List f(List, String). On WhatsApp 2.26.x that method no longer exists,
so sendMessage silently did nothing. This broke the Tasker "send message"
integration and any other caller.
Fix
Resolve the current text-message sending facade instead.
using the existing Unobfuscator and DexKit convention
service locator if it has not been constructed yet
Scope
WppCore.kt and Unobfuscator.kt only. No other features touched.
Testing
WhatsApp 2.26.35.75 on Android 14, module built from source. Messages are delivered
through the facade. The legacy path is left intact for older builds.
Note: this also fixes the underlying send path behind the scheduled-message
request in #787. I plan to open a separate PR adding scheduled messages on
top of this once it lands.