Android Meeting SDK 7.2.1: Development credentials rejected with error 5 / 124, Production credentials work

Description

Our Android Meeting SDK integration has been working in production for a long time. Around 12 November 2026 it began failing in our test environment with “Failed to initialize Zoom”, with no change on our side — no code change, no SDK upgrade, no configuration change.

We traced it to SDK authentication. us.zoom.sdk.ZoomError in the shipped AAR defines 5 = ZOOM_ERROR_AUTHRET_TOKENWRONG, and your documentation gives internal error 124 = token wrong, so the SDK is rejecting our JWT at auth and never reaches the meeting.

The decisive finding: our Development Client ID and Client Secret no longer authenticate, while the Production Client ID and Client Secret of the same app still do. Swapping only those two values, with nothing else changed, is enough to make it work. Both credential sets come from the same Marketplace app via the Development / Production toggle, not from two different apps.

Observed result:
onZoomSDKInitializeResult → errorCode = 5 (ZOOM_ERROR_AUTHRET_TOKENWRONG), internalErrorCode = 124

Which Android Meeting SDK version?

v7.2.1.43944. Authentication is by JWT. The same token is also rejected by the iOS Meeting SDK at sdkAuth(), so the behaviour is not Android-specific.

To Reproduce(If applicable)

Steps to reproduce the behavior:

  1. Generate a Meeting SDK JWT using our Development Client ID and Client Secret.
  2. Pass it as ZoomSDKInitParams.jwtToken and call ZoomSDK.initialize().
  3. See error: onZoomSDKInitializeResult returns errorCode 5, internalErrorCode 124.
  4. Generate the identical token using the Production Client ID and Client Secret of the same app, change nothing else, and initialization succeeds.

Troubleshooting Routes

We have already verified the following:

  1. The JWT is well formed. A token generated with the Development credentials decodes to:
    {
    “appKey”: “…”,
    “sdkKey”: “…”,
    “mn”: “…”,
    “role”: 0,
    “iat”: 1794942097,
    “exp”: 1795028497,
    “tokenExp”: 1795028497
    }
    Header is {“alg”:“HS256”,“typ”:“JWT”}. iat is about 14 minutes in the past, and exp = iat + 24h, inside the documented 30-minute to 48-hour window.

  2. The signature is correct. We recomputed HMAC-SHA256 over the token’s header.payload using the Client Secret copied directly from the Marketplace Development tab, and it reproduces the token signature exactly. We also tested the usual invisible-corruption cases (leading and trailing whitespace, \n, \r\n, case changes); all of them fail, so the match is exact rather than coincidental.

  3. The credentials are byte-identical to the Marketplace. Client ID is 21 characters, Client Secret is 32 characters, no non-ASCII characters, no lookalike 0/O or 1/l/I substitutions.

  4. Removing the optional “mn” and “role” claims (documented as optional for native) changes nothing — still 5 / 124.

  5. Features → Embed → Meeting SDK is enabled on both the Development and the Production environment of this app.

  6. The failure is not in our application code. Our backend mints the token and the mobile app only forwards it, so we took a token straight from the server debugger and fed it directly into the app, bypassing our own API entirely. Same failure.

  7. The SDK archive is not the issue — it contains no app identity, and the same binary authenticates successfully with the Production credentials.

We would note that the identical SDK binary and identical token-generation code succeed with the Production credentials, which already isolates the variable to the credential set rather than to our integration.

Smartphone:

  • Device: Google Pixel 9 Pro
  • OS: Android 17

Additional context

App Client ID (Development): Z8iB6UWIT82nmtbzx_Mkw
Date the failures began: approximately 12 November 2026

Happy to provide a full sample token, logs, or app details by DM.