When the Web SDK runs into an error, clicking on OK in the displayed dialog no longer redirects the user back to the provided leave_url parameter. There is a JS error in the console: [image] I could not reproduce this same issue using 1.6.0.

Hey @penar.musaraj, Please provide steps to reproduce this issue, and what OS and browser you are using. Thanks, Tommy

Step 1: Launch the SDK for a webinar that has not started yet. Step 2: Click on OK on the dialog: [image] Page goes black (dialog is dismissed), but does not redirect, and there is a console JS error: Uncaught TypeError: f.e.close is not a function.

Hey @penar.musaraj, I was able to reproduce this, nice find! We will work to fix this in our next release. (ZOOM-133218) Thanks, Tommy

Hello, I am seeing the same issue in the web sdk version 1.7.2, has it been addressed in the release or are there known work-arounds?

Hey @sean.mcahalan, I don’t believe this was fixed in 1.7.2. What error are you getting that is causing the popup? Thanks, Tommy

Hi @tommy, I too am facing the same issue when Clicked on OK button, when join fails. It throws an exception and screen goes blank. Below is the error object of joining errorCode: 1 errorMessage: “joining fail” method: “join” result: null status: false And Here is the error description ERROR TypeError: f.e.close is not a function at zoomus-websdk.umd.min.js:2 at index.js:11 at dispatch (applyMiddleware.js:35) at zoomus-websdk.umd.min.js:2 at index.js:11 at bindActionCreators.js:3 at onCancel (zoomus-websdk.umd.min.js:2) at k (zoomus-websdk.umd.min.js:2) at _ (zoomus-websdk.umd.min.js:2) at HTMLUnknownElement.callCallback (react-dom.development.js:149) defaultErrorLogger @ core.js:4002 push…/node_modules/@angular/core/fesm5/core.js.ErrorHandler.handleError @ core.js:4050 next @ core.js:26759 schedulerFn @ core.js:23735 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.__tryOrUnsub @ Subscriber.js:192 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.next @ Subscriber.js:130 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._next @ Subscriber.js:76 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber.next @ Subscriber.js:53 push…/node_modules/rxjs/_esm5/internal/Subject.js.Subject.next @ Subject.js:47 push…/node_modules/@angular/core/fesm5/core.js.EventEmitter.emit @ core.js:23719 (anonymous) @ core.js:26278 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke @ zone.js:391 push…/node_modules/zone.js/dist/zone.js.Zone.run @ zone.js:150 push…/node_modules/@angular/core/fesm5/core.js.NgZone.runOutsideAngular @ core.js:26215 onHandleError @ core.js:26278 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.handleError @ zone.js:395 push…/node_modules/zone.js/dist/zone.js.Zone.runTask @ zone.js:198 push…/node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask @ zone.js:498 invokeTask @ zone.js:1693 globalZoneAwareCallback @ zone.js:1719 invokeGuardedCallbackDev @ react-dom.development.js:199 invokeGuardedCallback @ react-dom.development.js:256 invokeGuardedCallbackAndCatchFirstError @ react-dom.development.js:270 executeDispatch @ react-dom.development.js:561 executeDispatchesInOrder @ react-dom.development.js:580 executeDispatchesAndRelease @ react-dom.development.js:680 executeDispatchesAndReleaseTopLevel @ react-dom.development.js:688 forEachAccumulated @ react-dom.development.js:662 runEventsInBatch @ react-dom.development.js:816 runExtractedEventsInBatch @ react-dom.development.js:824 handleTopLevel @ react-dom.development.js:4826 batchedUpdates$1 @ react-dom.development.js:20439 batchedUpdates @ react-dom.development.js:2151 dispatchEvent @ react-dom.development.js:4905 (anonymous) @ react-dom.development.js:20490 unstable_runWithPriority @ scheduler.development.js:255 interactiveUpdates$1 @ react-dom.development.js:20489 interactiveUpdates @ react-dom.development.js:2170 dispatchInteractiveEvent @ react-dom.development.js:4882 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:423 onInvokeTask @ core.js:26247 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:422 push…/node_modules/zone.js/dist/zone.js.Zone.runTask @ zone.js:195 push…/node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask @ zone.js:498 invokeTask @ zone.js:1693 globalZoneAwareCallback @ zone.js:1730 Show 16 more frames core.js:4002 ERROR Error: An error was thrown inside one of your components, but React doesn’t know what it was. This is likely due to browser flakiness. React does its best to preserve the “Pause on exceptions” behavior of the DevTools, which requires some DEV-mode only tricks. It’s possible that these don’t work in your browser. Try triggering the error in production mode, or switching to a modern browser. If you suspect that this is actually an issue with React, please file an issue. at Object.invokeGuardedCallbackDev (react-dom.development.js:208) at invokeGuardedCallback (react-dom.development.js:256) at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:270) at executeDispatch (react-dom.development.js:561) at executeDispatchesInOrder (react-dom.development.js:580) at executeDispatchesAndRelease (react-dom.development.js:680) at executeDispatchesAndReleaseTopLevel (react-dom.development.js:688) at forEachAccumulated (react-dom.development.js:662) at runEventsInBatch (react-dom.development.js:816) at runExtractedEventsInBatch (react-dom.development.js:824)ERROR TypeError: f.e.close is not a function at zoomus-websdk.umd.min.js:2 at index.js:11 at dispatch (applyMiddleware.js:35) at zoomus-websdk.umd.min.js:2 at index.js:11 at bindActionCreators.js:3 at onCancel (zoomus-websdk.umd.min.js:2) at k (zoomus-websdk.umd.min.js:2) at _ (zoomus-websdk.umd.min.js:2) at HTMLUnknownElement.callCallback (react-dom.development.js:149) defaultErrorLogger @ core.js:4002 push…/node_modules/@angular/core/fesm5/core.js.ErrorHandler.handleError @ core.js:4050 next @ core.js:26759 schedulerFn @ core.js:23735 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.__tryOrUnsub @ Subscriber.js:192 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.next @ Subscriber.js:130 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._next @ Subscriber.js:76 push…/node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber.next @ Subscriber.js:53 push…/node_modules/rxjs/_esm5/internal/Subject.js.Subject.next @ Subject.js:47 push…/node_modules/@angular/core/fesm5/core.js.EventEmitter.emit @ core.js:23719 (anonymous) @ core.js:26278 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke @ zone.js:391 push…/node_modules/zone.js/dist/zone.js.Zone.run @ zone.js:150 push…/node_modules/@angular/core/fesm5/core.js.NgZone.runOutsideAngular @ core.js:26215 onHandleError @ core.js:26278 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.handleError @ zone.js:395 push…/node_modules/zone.js/dist/zone.js.Zone.runTask @ zone.js:198 push…/node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask @ zone.js:498 invokeTask @ zone.js:1693 globalZoneAwareCallback @ zone.js:1719 invokeGuardedCallbackDev @ react-dom.development.js:199 invokeGuardedCallback @ react-dom.development.js:256 invokeGuardedCallbackAndCatchFirstError @ react-dom.development.js:270 executeDispatch @ react-dom.development.js:561 executeDispatchesInOrder @ react-dom.development.js:580 executeDispatchesAndRelease @ react-dom.development.js:680 executeDispatchesAndReleaseTopLevel @ react-dom.development.js:688 forEachAccumulated @ react-dom.development.js:662 runEventsInBatch @ react-dom.development.js:816 runExtractedEventsInBatch @ react-dom.development.js:824 handleTopLevel @ react-dom.development.js:4826 batchedUpdates$1 @ react-dom.development.js:20439 batchedUpdates @ react-dom.development.js:2151 dispatchEvent @ react-dom.development.js:4905 (anonymous) @ react-dom.development.js:20490 unstable_runWithPriority @ scheduler.development.js:255 interactiveUpdates$1 @ react-dom.development.js:20489 interactiveUpdates @ react-dom.development.js:2170 dispatchInteractiveEvent @ react-dom.development.js:4882 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:423 onInvokeTask @ core.js:26247 push…/node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:422 push…/node_modules/zone.js/dist/zone.js.Zone.runTask @ zone.js:195 push…/node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask @ zone.js:498 invokeTask @ zone.js:1693 globalZoneAwareCallback @ zone.js:1730 Show 16 more frames core.js:4002 ERROR Error: An error was thrown inside one of your components, but React doesn’t know what it was. This is likely due to browser flakiness. React does its best to preserve the “Pause on exceptions” behavior of the DevTools, which requires some DEV-mode only tricks. It’s possible that these don’t work in your browser. Try triggering the error in production mode, or switching to a modern browser. If you suspect that this is actually an issue with React, please file an issue. at Object.invokeGuardedCallbackDev (react-dom.development.js:208) at invokeGuardedCallback (react-dom.development.js:256) at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:270) at executeDispatch (react-dom.development.js:561) at executeDispatchesInOrder (react-dom.development.js:580) at executeDispatchesAndRelease (react-dom.development.js:680) at executeDispatchesAndReleaseTopLevel (react-dom.development.js:688) at forEachAccumulated (react-dom.development.js:662) at runEventsInBatch (react-dom.development.js:816) at runExtractedEventsInBatch (react-dom.development.js:824) I am using zoom websdk v1.7.2 Chrome 77 Windows 10 Regards, Junaid

Hi @junaid.razzaq, Thanks for reaching out, we’re aware of this bug and working on fixing this issue. For updates with our WebSDK, you can check out our upcoming features page[1] & change log[2]. 1 - https://marketplace.zoom.us/docs/guides/getting-started/stay-up-to-date/upcoming-changes/web-sdk 2 - https://marketplace.zoom.us/docs/guides/getting-started/stay-up-to-date/changelog

Hi @tommy, I too am facing the issue when Clicked on OK button, when join fails. It throws an exception and joining meeting time out. Please help me.

[image] This Screen will appear.

Hi All, Just wanted to update you on this feature. We are looking to fix this bug with our next WebSDK release tentatively scheduled for tomorrow. https://marketplace.zoom.us/docs/guides/getting-started/stay-up-to-date/upcoming-changes/web-sdk Thanks

Leave URL is not triggered when closing an error

Meeting SDK Web

tommy (Tommy Gaessler (PM VDI, Web, Linux, & Meeting SDK)) April 7, 2020, 5:01pm 13

Hey @shital.chourasia,

Please upgrade to the latest version and try again:

Thanks,
Tommy

Topic		Replies	Views
Constantly getting the error l.a.getJoinVoIPTimes is not a function while leaving the zoom meeting Web	3	686	August 18, 2020
None loading Zoom meeting Web	29	4736	July 1, 2021
Zoom Web SDK Firefox Crash on clicking "Join" button Web	4	1220	August 8, 2022
Web SDK 1.8.5 calling error callback after successful join Web	1	844	December 29, 2020
Zoom web sdk leave button not working Web	17	1753	August 15, 2022

Leave URL is not triggered when closing an error

Related topics