whatsapp: fix group reply trigger via canonical JID normalization#11469
Closed
RiptideV wants to merge 1 commit into
Closed
whatsapp: fix group reply trigger via canonical JID normalization#11469RiptideV wants to merge 1 commit into
RiptideV wants to merge 1 commit into
Conversation
904fb3e to
240008b
Compare
Contributor
|
Thanks for the fix, @RiptideV! This JID normalization is a real bug and the root-cause analysis is correct. However, this automated hermes-sweeper review found that the exact fix —
The upstream commit that introduced this fix is |
10 tasks
This was referenced May 20, 2026
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
3 participants
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.
Summary
Root cause
Baileys emits bot IDs with device suffixes while reply participant can arrive without suffix, so equality checks failed and group reply-to-bot did not trigger.
Validation
Files