Joining meeting timeout or Browser restriction on Browser SDK 4.0.7

Meeting SDK Type and Version
I have had this error on both meeting SDK 4.0.0 and 4.0.7 on the Web.

Description
I have an OAuth app (in draft) and a Server to Server app under Zoom marketplace. With meetings created by the S2S app under the developer account, I use the OAuth app to join them from the browser via Meeting SDK. This is where it goes wrong.

Error?

Upon joining the meeting, the SDK initialises fine at first and passes authentication (i.e. ZoomMtg.init and ZoomMtg.join succeeds). The browser enters the audio/video test page, with the “Join” button. After clicking on “Join”, I am greeted by the following error.

Joining Meeting Timeout or Browser restriction
Fail to join the meeting.
Error Code:1

On the Network tab I see no error, whilst on the Console the only error is a a websocket onclose event as follows:

zoom-meeting-4.0.7.min.js:2 
websocket onclose event:      
    type: close, code: 1006, reason:, timeStamp:3500.1900000572205, target:2      url: wss://zoomiad20624799187rwg.iad.zoom.us/wc/api/79995530951?ts=1759592318508&auth=vkt9R08x-SinNGCpK3FmYytKTEwSfvQf2XOq3MXaCY0&trackAuth=49YGo73HUN7wEfT5-7dc18E3ICvDaZTNnongViBCgus&mid=GD%2B7xBaiQKidsC4DQS5%2BBA%3D%3D&tid=v%3D2.0%3Bclid%3Dus04%3Brid%3DWEB_e277fa971d70f1fcd0c76ad058e8cb3e&browser=Chrome140&ZM-CID=454280f6-78ec-4cff-ad35-9cc349128274&lang=en-US&wccv=21.6.26&mpwd=FrpR4Q&jscv=4.0.7&isCamera=1&as_type=2&rwcAuth=MTc1OTU5MjMxOTAzMS4qJPMFDESi3wRxauSfKn5A3LDTlCqsXP-aCs8-6EgfTQ&islch=1&email=achan961117%40gmail.com&cfs=0&clientCaps=266854011&clientCapsEx=8728&clientOS=mac&audioFeature=12&rlb=1

Here is the tracking ID of the meeting where I ran into this error.
v=2.0;clid=us04;rid=WEB_e277fa971d70f1fcd0c76ad058e8cb3e

Troubleshooting Routes
I have already verified that it’s not an issue with meeting number, signature, password, or zak, as putting in invalid values for any of those would lead to a different and earlier failure in joining the meeting. Turning on debug mode, changing value for role.

@pinealan

I’ll reach out to you for your signature, some early findings indicate it might be an issue with number format

resolved. missing type=”JWT” in signature header