It can init some time. After that, ErrorCode = 1 and Internal ErrorCode = 0 because of tokenExp and exp had expired. Why doesnt onZoomAuthIdentityExpired fire ?!
When you are generating the JWT, are you using the same key and secret as when you are when initializing with the raw key/secret values? You mention API key + API secret, so I suspect that may be the issue. The SDK only accepts SDK credentials for initialization.
Hi @jon.zoom thank for your support.
I had confused between SDK app credentials and JWT app credentials.
Yes, for mobile app, must use SDK app credentials to generate jwt token.
It can work now. But when token expired, it return error 1 too. I think it must fire onZoomAuthIdentityExpired ?
Glad to hear it’s working with the correct credentials!
Regarding the JWT expiring, that depends on which type of expiration is happening. If you are reusing the same JWT multiple times in a session, reaching the exp field’s time will cause auth attempts to fail, as that represents when the JWT itself expires.
On the other hand, the tokenExp field represents when your authentication session expires, and should trigger the callback you mentioned.