I have no solution, but your signature looks good (decoded base64)
{"alg":"HS256","typ":"JWT"}
{
"sdkKey":"[REDACTED]",
"mn":"5868415858",
"role":0,
"iat":1660329547, -> Friday, 12 August 2022 18:39:07
"exp":1660336747, -> Friday, 12 August 2022 20:39:07
"appKey":"SSu3dBFMX5Qz7xp3SBwcyDkZByQ5uMlz6s874",
"tokenExp":1660336747 -> Friday, 12 August 2022 20:39:07
}
it’s the correct version for SDK JWT
the error then lies rather with the init of the meeting, do you use the SDK JWT there?
I know the web api and there you can choose between SDK JWT Signature and JWT Signature.
have a look - same error message - there was the “solution” cors header ??? strange
Thank you for confirmation of the JWT. The code that produces this error is the mobilertc-android-studio sample v5.11.3.9091.
I am at a loss how zoom can supply a sample sdk app that produces this error without a forum solution. Please help me better understand the next step to utilize the android SDK.
I was using the SDK Key and SDK Secret from my SDK App. I instead tried using the API Key and API Secret from my JWT App. The new JWT when used with the SDK sample app produces the same Error: 5 / 124.
I decided to start completely over and created a new zoom account and created a new Marketplace SDK app. Using the new SDK Key/Secret the error 5/124 has been eliminated. Great, it was personal. Anyway, I am now able to init the sdk but trying to join a meeting I am prompted for the meeting password for meetings that do not have passwords. I have previously detailed this issue here