Skip to content

[Bug]: Version drift banner says Update server when the macOS client is behind #5253

Description

@matheustimbo

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. Run the macOS desktop app on an older nightly build (example: 0.0.32-nightly.20260802.980).
  2. Connect to an environment whose server is on a newer nightly (example: 0.0.32-nightly.20260803.985).
  3. Open a conversation so the version-drift banner appears.

Expected behavior

The banner should recognize that the client is behind the server, tell the user to update this app, and offer an Update client action that runs the desktop updater. It must not offer updating/downgrading the server to the older client version.

Actual behavior

The banner title says "Client and server versions differ" and the body/CTA tell the user to Update server so they stay in sync. Clicking that action would target the client's older version on the newer server.

Example copy observed:

Client 0.0.32-nightly.20260802.980 is connected to … server 0.0.32-nightly.20260803.985. Update the … server so they stay in sync.

[Update server]

Impact

Major degradation or frequent failure

The CTA is inverted and can push a server downgrade when the desktop client simply needs an update.

Version or commit

0.0.32-nightly.20260802.980 client vs 0.0.32-nightly.20260803.985 server

Environment

macOS desktop app (nightly), connected to a remote/local server on a newer nightly

Workaround

Manually update/restart the macOS app (Check for Updates / install the newer desktop build) and ignore the "Update server" button.

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