whatsapp: bump whatsmeow to fix client outdated (405) sync failure - #387
Merged
Conversation
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.
The WhatsApp listener stopped syncing because WhatsApp servers now reject the pinned whatsmeow client version with a fatal "Client outdated (405)" error at connect. The library hardcodes a WhatsApp Web client version that WhatsApp periodically forces off.
This bumps whatsmeow (and its transitive dependencies) to the latest revision, which carries an updated client version accepted by the servers. Build, vet, and the full test suite pass with no source changes required. The daemon needs a restart to pick up the new build; existing session credentials remain valid, so no re-pairing is needed.