

The main code handling initiation of the SDK are here: private startMeeting(): void /login`, Unstable_runWithPriority vendor.js:346560įlushSyncCallbackQueueImpl vendor.js:324043 InvokeGuardedCallbackDev vendor.js:313139 W.IsSupportVideoDecodeHardwareAcceleration 1502_js_:1 ScheduleResolveOrReject polyfills.js:4380 NativeScheduleMicroTask polyfills.js:3676 Instrument.js:109 VP9?: true AMD?: false AMDdecodecheck: true enable720p?: true capacityfor720: trueġ502_js_:1 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'videodecodethreadnumb')Īt WebSocket.globalZoneAwareCallback (polyfills.js:4827:16) Instrument.js:109 Support video encode hardware acceleration: true GlobalZoneAwareCallback polyfills.js:4827

HandleUnhandledRejection polyfills.js:4201Īpi.microtaskDrainDone polyfills.js:4195

i s _ZoneDelegate.invoke ( at n ( at at _ZoneDelegate.invokeTask ( at nTask ( at drainMicroTaskQueue ( at ZoneTask.invokeTask ( at invokeTask ( at globalCallback ( at WebSocket.globalZoneAwareCallback ( (anonymous) vendor.js:9332 i s new ZoneAwarePromise ( at new t De Object. (1502_js_:1:101199)Īt _ZoneDelegate.invoke (polyfills.js:3487:26)Īt _ZoneDelegate.invokeTask (polyfills.js:3521:31)Īt drainMicroTaskQueue (polyfills.js:3700:35)Īt ZoneTask.invokeTask (polyfills.js:3606:21)Īt WebSocket.globalZoneAwareCallback (polyfills.js:4827:16) TypeError: Cannot read properties of null (reading 'videodecodethreadnumb')Īt g Generator._invoke e. TypeError: Cannot read properties of null (reading ‘videodecodethreadnumb’) instrument.js:109 >INIT JSMEDIASDK Task: Promise.then Value: TypeError: Cannot read properties of null (reading 'videodecodethreadnumb')Īt Generator._invoke (1502_js_:1:172158)Īt e.

This error seems to coincide with the scenarios where the button stays disabled: Has anyone seen anything like this? Or have thoughts as to where to check to diagnose? We’ve found with all users so far who have tested the newer version that they see the button disabled initially with the only optin to leave and rejoin until it works. I’ve upgraded the version of Zoom’s websdk we’re using from 2.6.0 > 2.12.2 to incorporate the changes for switching to using the SDK client id/secret.
