Understood, thank you for clarifying that. Based on another forum post, it seems this issue is related to the tpc field of your JWT. It has to match the sessionName value provided when trying to join the session. If that is not the case, could you change them to match and let me know if the issue is resolved? This is the mentioned post.
As per the docs sessionName has to be specified and not tpc or topic. I was able to get the sample app working with the token generated by our own app.
We have found the root cause to be calling ZoomVideoSDK.getInstance().cleanup() after ZoomVideoSDK.getInstance().leaveSession(true).
As per the docs, it is not clear what this method actually does. It would be really helpful if you could elaborate on what it does and if it is okay to not call this method. The sample app doesn’t call this method.
I apologize for the delayed response. I see that you were able to get the sample app working with your generated token, but you’re still having trouble with the linked application. It’s mentioned here (under the payload section, the ‘tpc’ row) that the topic in the payload should be the same as the one in the join session context when trying to join the meeting. After checking with engineers, the error you’re getting is more likely to be related to a mismatch there, rather than the methods you mentioned. Have you had a chance to check your ‘tpc’ value for your JWT and ensure that it matches the session name you used?