SDKAuth() succeeds synchronously but onAuthenticationReturn callback never fires (Linux Meeting SDK, headless-linux-sample)

API and Webhooks Users and Groups
1

Title: SDKAuth() succeeds synchronously but onAuthenticationReturn callback never fires (Linux Meeting SDK, headless-linux-sample)

SDK: Zoom Meeting SDK for Linux (arm64), using the official meetingsdk-headless-linux-sample (GitHub - zoom/meetingsdk-headless-linux-sample: A demo on creating a headless meeting client using the Zoom Meeting SDK for Linux and Docker · GitHub), unmodified auth flow.

Client ID: KxrDD2uxSeu9kfkGgeAKOA

App type: General App (User Managed), Meeting SDK feature enabled under Features → Embed, “Are you developing a programmatic join use case?” enabled, app installed/authorized on my own account (Shared Access Permissions: Authorized).

Environment: Docker container, Ubuntu 24.04, arm64 (Apple Silicon host via Docker Desktop), running via docker compose. GLib main loop is running (g_main_loop_run in main.cpp, per the official sample).

Steps to reproduce:

  1. Fill config.toml with Client ID/Secret + join-url for a meeting I am hosting on my own account.
  2. Run docker compose up.
  3. App builds and runs successfully: prints ✅ configure, ✅ initialize, ✅ authorize (this is only the synchronous return of SDKAuth(), meaning the call was accepted).
  4. AuthServiceEvent::onAuthenticationReturn is NEVER called afterward — not AUTHRET_SUCCESS, not any error code, not even AUTHRET_OVERTIME. I’ve waited 30+ minutes and restarted multiple times; the process stays alive (confirmed via strace, still polling normally) with established TLS connections to Zoom’s servers, but no callback ever fires.

What I’ve already ruled out:

  • Network egress works (verified curl to zoom.us from inside the container succeeds).
  • JWT generation logic and clock sync are correct (host/container clocks match, JWT exp is 24h).
  • GLib event loop is present and running (this is the official sample’s approach).
  • App type/config: General App with Meeting SDK + programmatic join enabled, installed/authorized on my own account.
  • Not a build/environment issue — this is a fresh official Ubuntu 24.04 arm64 build with no code modifications.

Question: Is there an account-level Meeting SDK entitlement that needs separate activation (similar to AUTHRET_ACCOUNTNOTENABLESDK reported by other users), and if so, how can I check/request it for my account? Or is there another known cause for onAuthenticationReturn silently never firing under these conditions?

Happy to share full logs on request.

2

@H_o thanks for reporting this, are you able to share the logs in the docker instance? it is found in ~/.zoomsdk

internal reference
ZSEE-213392

3

@H_o this is a known issue and will be fixed in 7.2 released later this month

4

When do you expect to release a fix for this issue?

5

Hi @H_o the new version is available on marketplace. There is now a combined / unified Linux sdk for arm and x64