Zoom Meeting SDK sdkAuth() Failure — Support Report

Meeting SDK
1

Zoom Meeting SDK sdkAuth() Failure — Support Report

Summary

ZoomSDKAuthService.sdkAuth(context:) synchronously returns ZoomSDKError_Failed (rawValue 1) — no async delegate callback fires at all — for a well-formed JWT signed with this app’s Client Secret. Reproduces identically in our own app and in Zoom’s own unmodified ZoomSDKSample (macOS), so this is not an application bug.

Environment

  • Meeting SDK version: 7.1.5.84750 (macOS, universal)
  • App: General app 542 (Platform Studio / new unified app model), User-managed, Beta
  • Client ID: wmXLqTogQLB4tcCxIgQA
  • OS: macOS 26.5 (arm64)

Timeline

  • Worked correctly earlier the same day (same Zoom account, different meeting ID).
  • Started failing consistently later the same day; has not self-recovered after ~10+ hours, ruling out a short-lived rate limit.
  • The Zoom account that owns this Marketplace app and the account hosting the test meeting are the same account (confirmed) — so this should not be affected by the “apps joining meetings outside their account” (OBF/ZAK) policy per Zoom’s own documentation.

What’s been ruled out

  • JWT correctness: payload is {appKey, iat, exp, tokenExp} (also tested with added sdkKey/role claims — no difference either way). Freshly issued each attempt, exp 30 min out, signed HS256 with the Client Secret shown in Marketplace. Decoded and manually verified structure/timing on every attempt.
  • needCustomizedUI: confirmed false (this was the fix for an earlier, different bug this same week — reproduced and fixed once already, not the current issue).
  • initSDK params: enableLog=true, logFileSize=5, zoomDomain="zoom.us" — initSDK itself returns ZoomSDKError_Success; only the subsequent sdkAuth() call fails.
  • Local session state: cleared ~/Library/Application Support/<app>/data (ZoomSDK’s local session DB) for both our app and ZoomSDKSample — no change.
  • Deliberately-wrong-signature JWT: correctly rejected via the async delegate path (onZoomSDKAuthReturn with a non-success ZoomSDKAuthError), confirming that failure path works — this is a different, synchronous failure before any callback fires.
  • Network: JWT-issuing backend reachable and returning 200 with valid tokens; no reachability issue observed to zoom.us/marketplace.zoom.us. (No outbound call to zoom.us is even observed in the unified system log at the moment sdkAuth() fails — the failure appears to happen before any network round-trip.)
  • Marketplace configuration: reviewed Basic Information, Features → Access/Surface, and Scopes — no Meeting-SDK-specific toggle found anywhere (only user:read:zak and zoomapp:inmeeting scopes are present, both unrelated to the classic sdkAuth() JWT flow). “Zoom account eligibility: No additional requirements” on the public listing.

Ask

Given ZoomSDKError_Failed is a generic bucket and no async callback ever fires, we have no further client-side signal to debug. Could support check, on Zoom’s side, for this account/app (Client ID wmXLqTogQLB4tcCxIgQA):

  1. Any account-level flag, hold, or review requirement blocking Meeting SDK auth
  2. Whether this “General app” (Platform Studio) type still supports the classic SDK-Key/Secret JWT sdkAuth() flow, or whether that’s been deprecated/migrated away from for apps created in this newer format
  3. Server-side logs for sdkAuth attempts from this Client ID around the failure window
2

@Akihiro2 I’ll PM you for more details