Linux Meeting SDK: SDKAuth succeeds synchronously but onAuthenticationReturn never fires (General app, JWT auth)

Linux Meeting SDK: SDKAuth succeeds synchronously but onAuthenticationReturn never fires (General app, JWT auth)

SDK version: 7.1.5.4434 (Linux, arm64), libmeetingsdk.so
App type: General app, Meeting SDK enabled under Features > Embed, “programmatic join” toggle ON, app authorized on the account via Local Test’s “Add app” OAuth flow.
Environment: Ubuntu 22.04 container (Docker Desktop on Apple Silicon, arm64), outbound internet access confirmed working.

Symptom: IAuthService::SDKAuth(AuthContext&) returns SDKERR_SUCCESS synchronously, but IAuthServiceEvent::onAuthenticationReturn is never invoked — not with a success code, not with a failure code — even after waiting up to 120 seconds. This happens identically whether the JWT is well-formed and correctly signed, or deliberately invalid, suggesting the response is silently dropped rather than being JWT-content-specific.

JWT structure being sent: Header {“alg”:“HS256”,“typ”:“JWT”}; payload {appKey: , mn, role: 1, iat: now-30s, exp: iat+7200, tokenExp: iat+7200}, HS256-signed with the app’s Client Secret — matches the documented native-platform claim shape.

What’s been ruled out: iat clock skew (backdated 30s per a similar forum resolution); app not authorized (completed Local Test “Add app” flow); programmatic join disabled (confirmed enabled); anonymous-join review requirement (not applicable — testing entirely within our own developer account); wrong meeting number for ZAK-based start (fixed to use the user’s PMI per the user-types doc, no change in SDKAuth behavior as expected); network/connectivity (strace confirms successful connect() to a Zoom IP on port 443).

No diagnostic info available: GetZoomLastError() returns nullptr after timeout. The SDK’s own log file is written but appears to be an encrypted/binary internal format.

Question: What would cause onAuthenticationReturn to never fire at all for a General app’s JWT-based SDKAuth on Linux, given confirmed connectivity and a Local-Test-authorized, programmatic-join-enabled app? Is there an additional account/app-level entitlement beyond “programmatic join” that must be requested/approved before SDKAuth actually completes?

@Bryan1 I’ll investigate this. Meanwhile if you have the SDK logs in ~/.zoomsdk it will be super helpful.

Internal reference ZSEE-213392

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

Here are the logs if you would still like them

(Attachment zoom-meetingsdk-sdkauth-log.log is missing)

I tried but can’t upload the logs to the support ticket.

@Bryan1 thanks for reporting this.

Any news on this? It is getting close to the end of the month and I haven’t seen 7.2 yet.

@Bryan1 there should be a Linux-All with version 7.2 . It comes with ARM and x64 SDKs

Good news! that SDK version works! Thank you

Bad news… I have a new error:
time=“2026-09-26T19:59:44Z” level=error msg=“Bot 52 failed at create user: Zoom POST /users failed (400): {“code”:3412,“message”:“Your request to add a basic user could not be approved at this time because your account has reached the permitted maximum number of 20 basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to add another user.”}” source=console

I thought I could create/destroy as many free accounts as needed. But it looks like we have an account limit for free accounts? That seems really confusing.

I’d check the callback registration and SDK initialization first. Since SDKAuth() succeeds but onAuthenticationReturn never fires, it may be an event-handling or Linux ARM64 SDK issue rather than the JWT itself.

The new build was the solution. I’ve just run into a hard limit in my account of 20 Basic Users. The SDK doesn’t allow you to create more than that. It looks like I will have to work with my Account Rep to get that changed.