We are working on 2 apps that need to work hand-in-hand. The solution allows people to connect their zoom account to lms platform and later use saved account to schedule meetings (1st app) and allow participants to join using browser (2nd app).
Adding account and scheduling a meeting - it works fine. The problem we face is when the user is trying to join the meeting (host or participant) - get signature error
as the app has not been published - we can test using our developer account and the error does not appear. However, during functional review the error appears, which cannot be replicated by our side.
Has anyone faced such problem or may suggest possible solutions?
How you are creating the signature ?
Have you tried decoding your signature like what values are there.
Check it on https://jwt.io/ see if the token is valid and the values are also valid.
we are creating the signature as defined Meeting SDK Auth
the token is valid (the only one we have for 1 account we can test on) and everything is working.
would anyone have a suggestion how to solve the problem that only zoom testers are facing? and we are unable to see due to the test account?
@kwiga.developer can you share a sample of your JWT token? And tag me in your response
@kwiga.developer , could you share a screenshot of your meeting sdk app as well? I would need to check on the sdk Key / Client ID
@kwiga.developer , are you able to replicate this issue from your side?
@chunsiong.zoom no, we cannot replicate this issue. Our account is connecting and working, the issue arises when we sent app for approval and the Review team returned with an error. Per their recommendation we reached out on this forum, as we are unable to understand what the problem is , how to replicate it and consequently how to fix it.
what is the way forward? We are sort of locked out of any progress. @chunsiong.zoom
@chunsiong.zoom we sent reply i pm and didnt hear back