Web SDK 4.0.0 got break out meeting room

Description
I’m using web sdk CDN. Some users got breaking out meeting room on web.

Browser Console Error
externalController sdk init
VM21 meeting.js:2 DOM fully loaded and parsed
VM25 zoom-meeting-4.0.0.min.js:2 checkSystemRequirements is no longer maintained, please use checkFeatureRequirements to get the supported/unsupported features on your platform.
VM25 zoom-meeting-4.0.0.min.js:2 Zoom support you browser. Chrome/139.0.0.0
VM25 zoom-meeting-4.0.0.min.js:2 You browser support below features
VM21 meeting.js:48 {“browserInfo”:“Chrome/139.0.0.0”,“browserName”:“Chrome”,“browserVersion”:“139.0.0.0”,“features”:[“viewSharing”,“screenShare”,“computerVideo”,“computerAudio”,“callIn”,“callOut”,“chat”,“closedCaption”,“QA”,“POLLING”,“BREAKOUT”,“GALLERY”]}
VM25 zoom-meeting-4.0.0.min.js:2 langDir https://source.zoom.us/4.0.0/lib/lang
VM25 zoom-meeting-4.0.0.min.js:2 success load tp
VM25 zoom-meeting-4.0.0.min.js:2 success load webim
VM25 zoom-meeting-4.0.0.min.js:2 success load jsmedia
VM25 zoom-meeting-4.0.0.min.js:2 load success https://source.zoom.us/4.0.0/lib/lang/vi-VN.json
VM25 zoom-meeting-4.0.0.min.js:2 success load tp
VM25 zoom-meeting-4.0.0.min.js:2 pre load wasm success: https://source.zoom.us/4.0.0/lib/av/video.mtsimd.wasm
VM25 zoom-meeting-4.0.0.min.js:2 pre load wasm success: https://source.zoom.us/4.0.0/lib/av/audio.simd.wasm
VM25 zoom-meeting-4.0.0.min.js:2 init tp success
VM40 js_media.min.js:2 handleRendererTypeInProps() final rendererType=3 gpuBlacklist=undefined
VM40 js_media.min.js:2 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: true capacityfor720: false
c22318c3-3591-4d82-9e50-3c8bce4ce753:1 Video Version: 3727
VM40 js_media.min.js:2 handleRendererTypeInProps() final rendererType=3 gpuBlacklist=undefined
16fd003c-2179-4e82-bd17-a8ef1175224c:1 Audio Version: 3727
b3bd33e9-51fa-45b0-8e38-faedc98bbef1:1 Video Version: 3727
1346012a-7b1d-480f-972c-d2c0957f6d9b:1 Sharing Version: 3727
VM40 js_media.min.js:2 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: true capacityfor720: true
dc89470e-45f7-4031-9561-de93f285b390:1 consume interval 6
chunk-vendors.c6625968.js:53 [8/20/2025, 13:49:39] [v1.64.4] getCurrentJSBridgeObject undefined
chunk-vendors.c6625968.js:53 [8/20/2025, 13:49:39] [v1.64.4] advancedDiagnosticsAdapter enabled!
chunk-vendors.c6625968.js:53 [8/20/2025, 13:49:39] [v1.64.4] start register master unifySdk… {sdkObject: undefined, sdkName: ‘unifySdk’, bridgeOptions: {…}}
chunk-vendors.c6625968.js:53 [8/20/2025, 13:49:39] [v1.64.4] register master unifySdk successfully! {sdkObject: {…}, unifySdkObject: {…}, sdkName: ‘unifySdk’, bridgeOptions: {…}}
chunk-vendors.c6625968.js:53 [8/20/2025, 13:49:39] [v1.64.4] Iframe request webview.ready__id_1755672579650_94429d46aa44d8 {iframeWindow: null, functionName: ‘webview.ready’, params: {…}, timeout: 60, raceMode: false, …}
VM84 zoomus-websdk-main-client.umd.min.js:84 [zapp] no handler for: zmAppBridgeSub 998803
app.9120d92d.js:1 zmAppBridgeSub failed: Error: zmAppBridgeSub took longer than 10000ms to respond
at app.9120d92d.js:10:14795
app.9120d92d.js:1 handler event registered successfully.
app.9120d92d.js:1 window clientVersion 5.13.10.1
app.9120d92d.js:1 IS_IN_MEETING_CLIENT true
app.9120d92d.js:1 ~~~~~ zmCommonAicAction {aicFreeTrialStatus: 1}
app.9120d92d.js:1 ~~~~~ zmCommonAicAction {aicUpgradeToPro: 1}
app.9120d92d.js:1 -----updateClientSessionInfo------ nativeType in-meeting
app.9120d92d.js:1 zmGetClientInfo success {context: ‘LAUNCHER’, dataFormat: ‘EEE, MMM d, yyyy’, dateFormatMMdd: ‘EEE, MMM d’, hourUnit: ‘24’, os: ‘windows’, …}
app.9120d92d.js:1 zmGetUserInfo success {avatar: null, isOriginalHostCurrentHost: 0, jid: ‘vc.daymai.vn’, originalHost: false, userId: 16790528, …}
app.9120d92d.js:1 ~~~~~ get IN Meeting init Data succes
app.9120d92d.js:1 configure success
app.9120d92d.js:1 initSnowplow {url: undefined, client_version: ‘5.13.10.1’}
AIC.ca57ec44.js:12 ----- index pageType -1 undefined
app.9120d92d.js:1 Sending payload to zmAppBridgePub: {service: ‘unifywebview’, data: ‘{“jsCallId”:“1HrTPTeJ5IoS”,“action”:“DLAct_GetFeatureCapability”,“params”:{}}’}
app.9120d92d.js:1 ~~~~~ zmCommonAicAction {loadFinish: 1}
AIC.ca57ec44.js:12 caic domain undefined
VM84 zoomus-websdk-main-client.umd.min.js:84 [zapp] no handler for: zmAppBridgePub 998803
VM84 zoomus-websdk-main-client.umd.min.js:84 [zapp] no handler for: zmGetAllServices 998803
AIC~FileSelector~FreeToPaid~JobDetail~MeetingOnboarding~SendToChat~Summary.414d4f59.js:1 refreshMMRTokenForAIC, token Wed Aug 20 2025 13:49:58 GMT+0700 (Indochina Time)
AIC~FreeToPaid.5d0308d5.js:1 ===zmGetAICOption===
AIC~FreeToPaid.5d0308d5.js:1 optionHelper
AIC~FreeToPaid.5d0308d5.js:1 ===zmMyMeetingQueryPrivileges===
AIC~FreeToPaid.5d0308d5.js:1 ~~~~~ getAICStatusInMeeting origin {status: ‘stopped’} {status: ‘stopped’} {settings: Array(5), currentSetting: 2, locked: true}
AIC~FreeToPaid.5d0308d5.js:1 ~~~~~ getAICStatusInMeeting
AIC.ca57ec44.js:12 ----- index pageType 4 -1
AIC.ca57ec44.js:12 === Starting ZPNS Connection ===
AIC.ca57ec44.js:774 %%% enter conversation message page 4
AIC.ca57ec44.js:774 versionUpdatePage false
AIC~FileSelector~FreeToPaid~JobDetail~MeetingOnboarding~SendToChat~Summary.414d4f59.js:1 refreshMMRTokenForAIC, token Wed Aug 20 2025 13:49:59 GMT+0700 (Indochina Time)
app.9120d92d.js:1 getAvailableNativeSerivceHubSkills Error: zmGetAllServices took longer than 10000ms to respond
at app.9120d92d.js:10:14795

Which Web Meeting SDK version?
4.0.0

To Reproduce(If applicable)
Just join meeting via web, and wait about some minutes (3mins)

Screenshots

Device (please complete the following information):

  • Browser: Chrome
  • Browser Version 139.0.7258.128 (Official Build) (64-bit)

Someone can help me?

@thaopv do have have use SAB? Meeting SDK - web - SharedArrayBuffer if not. could you help take recording. and have you see loading UI ?

from screenshot. looks like SAB iframe config issue

Why Both Pages Need Headers

SharedArrayBuffer requires the entire browsing context to be cross-origin isolated. This means:

  1. Parent page must be cross-origin isolated

  2. Iframe page must also be cross-origin isolated

  3. All resources loaded by either page must comply with the policy

Header Configuration

Parent Page Headers:

http

Cross-Origin-Embedder-Policy: credentialless
Cross-Origin-Opener-Policy: same-origin

Iframe Page Headers (same headers):

http

Cross-Origin-Embedder-Policy: credentialless
Cross-Origin-Opener-Policy: same-origin