Gmail OAuth token exchange: invalid_grant / Malformed auth code with FluentSMTP

We are connecting one owner-controlled Gmail account to a WordPress site using FluentSMTP 2.4.1 and need help isolating a failed authorization-code exchange.

Configuration checked:

Latest server-side trace, 2026-10-25 23:48:35 UTC:
POST https://accounts.google.com/o/oauth2/token
HTTP 400; error: invalid_grant
Displayed error description: Malformed auth code.
There was one token-endpoint request for this save attempt.

The callback code is manually transferred into the plugin field labelled Access Token (internally auth_token). This transfer occurs in a cloud browser viewed from an Android phone, and clipboard transfer is not yet verified. Earlier attempts returned Bad Request. We cannot claim a fresh, intact code has been successfully transferred.

The hosting provider checked server clock and outbound HTTPS and reported normal operation. REST API and loopback checks pass. No Gmail connection has been saved successfully.

Questions:

  1. Does Malformed auth code specifically indicate that the submitted code string is syntactically invalid, or can expiration, reuse, or client/redirect mismatch produce the same description?
  2. Which non-secret diagnostics (for example length, prefix-shape checks, whitespace/encoding checks) can safely distinguish these cases without recording the code or tokens?
  3. The plugin sends JSON with Content-Type application/http to the legacy token endpoint. Is that supported for this exchange, or must it use form-urlencoded and oauth2.googleapis.com/token?

We want to identify the failing step before asking the owner to repeat sign-in again. Please advise on the most targeted diagnostic or supported correction.