Skip to content

WA Web Apr-24 fixes shipped at oxidezap/whatsapp-rust; wa-rs 0.2.0 is behind #1

Description

@alexandme

Courtesy ping from a downstream. ZeroClaw (an agent runtime) pins wa-rs = "0.2". Filing this so the next person who searches has a trail.

Around 2026-04-24, WhatsApp Web rotated handshake and device-props expectations. On wa-rs 0.2.0 the symptom is: pair code succeeds, no inbound messages flow. Tracked at zeroclaw-labs/zeroclaw#6246.

The live upstream is oxidezap/whatsapp-rust (renamed from jlucaso1/whatsapp-rust; GitHub redirects). 39 commits since 2026-04-20. Fixes that shipped:

  • #586 (DevicePropsOverride, cb8d260) — breaking
  • #594 (ADV HMAC verify, 06809e1)
  • #598 (Noise_IK + XXfallback, 158da6d) — the actual handshake fix
  • #601 (PlatformType normalization, 4b8835b) — breaking

This fork branched from jlucaso1/whatsapp-rust@28d8e00 on 2026-02-17 and has stayed quiet since 2026-02-20. wa-rs 0.2.0 on crates.io won't pair against the post-Apr-24 server without those patches.

Two small things, if useful:

  1. A README pointer to oxidezap/whatsapp-rust so the next person searching wa-rs finds the live upstream.
  2. Archive the repo if you don't intend to keep it current.

I can open a one-line README PR if that's easier. Either way, thanks for the original rebrand work.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions