fix(desktop): WhatsApp Web rejects a current Chromium browser as outdated #5

Activity

1. OsirisMedici commented on Oct 28, 2026

   

   OsirisMedici

   on Oct 28, 2026

   OwnerAuthor

   More actions

   Note

   🤖 gpt-6.1-sol responding on behalf of OsirisMedici

   Title

   Regression reproduced before implementation.

   Domain / Area

   T3 Code desktop browser sessions.

   What Exactly Happened

   The initial WhatsApp request retains Electron/44.9.3. WhatsApp's parser reads this as Electron 44 even though Chromium is version 152.

   What We Did

   Added regression coverage in the existing BrowserSession.test.ts suite for the initial request/page identity, leaving WhatsApp, exact-origin matching, subframe/resource isolation, and lowercase header handling.

   Outcome

   Ran bun run test src/preview/BrowserSession.test.ts from apps/desktop against the unchanged implementation: 3 failed, 9 passed. The first failure shows the outgoing header still containing the Electron token. Implementation is next.

   Reused existing installed dependencies after comparing the root, desktop, shared, and contracts dependency declarations. No lockfile or dependency-version changes. No running application restart or installed-build mutation.

   Proof of work (screenshots)

   The original failure screenshot was supplied in the task. This update is backed by the regression-test output; no additional screenshot uploaded.
2. OsirisMedici commented on Oct 28, 2026

   

   OsirisMedici

   on Oct 28, 2026

   OwnerAuthor

   More actions

   Note

   🤖 gpt-6.1-sol responding on behalf of OsirisMedici

   Title

   Source fix implemented and verified with Electron 44.9.3.

   Domain / Area

   T3 Code desktop browser request identity and guest preload.

   What Exactly Happened

   A native Electron fixture caught an important constraint: calling webContents.setUserAgent during onBeforeSendHeaders aborts the pending navigation with ERR_ABORTED (-3). The initial mocked tests did not reveal this. That implementation was replaced before handoff.

   What We Did

   • Added an exact-origin identity helper for https://web.whatsapp.com that removes only the Electron token and retains the actual Chrome version and T3 identity.
   • Restricted the request interceptor to WhatsApp Web. It adjusts the outgoing User-Agent without changing the session or WebContents identity.
   • Applied the matching navigator.userAgent and navigator.appVersion values in the existing preview preload, before website scripts execute.
   • Kept other origins, native client hints, Default-profile storage, and unrelated tabs unchanged.
   • Updated the existing browser-session tests to cover both the request and page identity, exact-origin boundaries, other origins and subframes, lowercase/missing headers, and background requests. They also prevent reintroducing the navigation-aborting setter.

   Outcome

   Source verification passed.

   • bun run test src/preview/BrowserSession.test.ts from apps/desktop: 13 passed.
   • Scoped desktop typecheck: passed.
   • Lint and formatting for all four changed source/test files: passed.
   • git diff --check: passed.

   Native runtime verification passed. An isolated, hidden Electron 44.9.3 process used Chromium 152.0.7977.167 and a local HTTP fixture. It exercised the production request handler and identity helper, mapping the local fixture URLs to the test origins. Verified the first outgoing request, identity observed by the first inline script, unchanged Chromium 152 client hints, native identity on other-origin resources and a separate tab, and native request/page identity after navigating away.

   This was a local native fixture, not a real WhatsApp acceptance test. No login, message, profile migration, running-app restart, installed-build replacement, commit, push, or PR was performed. The source changes are local and uncommitted. Keep this issue open until the updated desktop build reaches WhatsApp's login screen in the real product.

   Proof of work (screenshots)

   No new screenshots are claimed. The original failure screenshot is in the task. Native runtime transcript:

   Electron: 44.9.3
   Chromium: 152.0.7977.167
   Initial WhatsApp request identity: PASS
   Identity in first inline page script: PASS
   Native Chromium 152 client hints preserved: PASS
   Other-origin resource identity: PASS
   Unrelated tab isolation: PASS
   Native session identity: PASS
   Native request and page after leaving WhatsApp: PASS
   

   Manual acceptance on an updated desktop build: open WhatsApp Web in Default, confirm the QR/login screen replaces the unsupported-browser message, then navigate the same tab to another site and confirm its native Electron identity. This acceptance remains outstanding.