Hi Zoom Developer Community,
I am building a native macOS application using the **Meeting SDK for macOS (v6.7.2.72402)**.
I am running into a persistent **Auth Failed (Error 1)** (`ZoomSDKError_Failed`) during initialization, despite ensuring my JWT is correctly formatted.
**Setup:**
- **OS:** macOS (Apple Silicon)
- **SDK Version:** 6.7.2.72402
- **App Type:** “General App” (Marketplace) with “Meeting SDK” embed feature enabled.
- **Auth Method:** JWT (since direct SDK Key/Secret params seem deprecated/removed in headers).
**Code Snippet (Obj-C++):**
```objectivec
ZoomSDKInitParams *params = [[ZoomSDKInitParams alloc] init];
params.enableLog = YES;
params.zoomDomain = @“zoom.us”;
ZoomSDKError ret = [[ZoomSDK sharedSDK] initSDKWithParams:params]; // Returns Success
ZoomSDKAuthService *auth = [[ZoomSDK sharedSDK] getAuthService];
auth.delegate = self;
ZoomSDKAuthContext *authContext = [[ZoomSDKAuthContext alloc] init];
authContext.jwtToken = @“<MY_GENERATED_TOKEN>”;
[auth sdkAuth:authContext]; // Calls onZoomSDKAuthReturn
```
**The Issue:**
`onZoomSDKAuthReturn` is always called with `ZoomSDKAuthError_AuthFailed` (1).
**What I Have Tried:**
1. **Clock Skew:** I verified `iat` is set to `now - 120s` to account for drift.
2. **Payload:** I am using the standard payload required for SDK initialization:
\`\`\`json
{
“appKey”: “”,
“iss”: “”,
“iat”: <epoch - 120>,
“exp”: <epoch + 24h>,
“tokenExp”: <epoch + 24h>
}
\`\`\`
3. **App Keys:** I am using the Client ID/Secret from my “General App” page (App Credentials tab).
**My Question:**
Does the **macOS Meeting SDK** support authentication via JWT using keys from a **“General App”** (with Meeting SDK Embed turned ON)?
Or **MUST** I create a legacy “Meeting SDK” app type specifically?
I suspect my keys (which are technically OAuth Client Credentials) are being rejected by the SDK auth endpoint because it expects legacy SDK keys, but the documentation implies JWT is the universal standard now.
Any guidance on the expected JWT payload for a “General App” initializing the Native SDK would be greatly appreciated!