# Meeting SDK not loading the meeting with React 19

**URL:** <https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507>\
**Category:** Meeting SDK\
**Created:** [February 19, 2025, 4:47am UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507 "2025-02-19T04:47:49Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anujeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/anujeet/32/49249_2.png) [@Anujeet](https://devforum.zoom.us/u/Anujeet)\
**Post date:** [February 19, 2025, 4:47am UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/1 "2025-02-19T04:47:49Z")

</div>

We are using **Zoom Meeting SDK v3.11.2** with **React 19**.

After upgrading to **React 19** , our embedded meetings view no longer loads meetings. When the SDK initializes, we only see a **black screen** , and no meeting interface appears.

In the browser console, we are encountering a **TypeError** related to `ReactCurrentBatchConfig` being undefined.

Here is the full error message from the console:

```auto
GET http://localhost:3000/en/zoom?link=https://us-6web.zoom.us/j/7078813268?pwd= 500 (Internal Server Error)
handler @ webpack-internal:///…/client-entry.js:33
zoomus-websdk-zoommtgMain.umd.min.js:2 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'ReactCurrentBatchConfig')
    at 22551 (zoomus-websdk-zoommtgMain.umd.min.js:2:2070751)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 40961 (zoomus-websdk-zoommtgMain.umd.min.js:2:2177962)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 5338 (zoomus-websdk-zoommtgMain.umd.min.js:2:2177652)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 38568 (zoomus-websdk-zoommtgMain.umd.min.js:2:1680793)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 62778 (zoomus-websdk-zoommtgMain.umd.min.js:2:1754658)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 21819 (zoomus-websdk-zoommtgMain.umd.min.js:2:1723130)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 11447 (zoomus-websdk-zoommtgMain.umd.min.js:2:1577530)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 24472 (zoomus-websdk-zoommtgMain.umd.min.js:2:1754259)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 27383 (zoomus-websdk-zoommtgMain.umd.min.js:2:1700664)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 92987 (zoomus-websdk-zoommtgMain.umd.min.js:2:1704155)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 83825 (zoomus-websdk-zoommtgMain.umd.min.js:2:1701687)
    at a (zoomus-websdk.umd.min.js:2:878752)
    at 40926 (zoomus-websdk-zoommtgMain.umd.min.js:2:1676073)
    at a (zoomus-websdk.umd.min.js:2:878752)
22551 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
40961 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
5338 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
38568 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
62778 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
21819 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
11447 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
24472 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
27383 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
92987 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
83825 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
40926 @ zoomus-websdk-zoommtgMain.umd.min.js:2
a @ zoomus-websdk.umd.min.js:2
Promise.then
eval @ zoomus-websdk.umd.min.js:2
startMeeting @ ZoomMeeting.tsx:30
ZoomMeeting @ ZoomMeeting.tsx:61

```

We hope you can look into this issue. Thank you for your attention to this matter.

---

<div class="post-metadata">

**Author:** ![Sumved](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sumved/32/68085_2.png) [@Sumved](https://devforum.zoom.us/u/Sumved)\
**Post date:** [March 20, 2025, 7:46pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/2 "2025-03-20T19:46:48Z")

</div>

Were you able to solve this issue?

---

<div class="post-metadata">

**Author:** ![tcobb](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tcobb/32/62467_2.png) [@tcobb](https://devforum.zoom.us/u/tcobb)\
**Post date:** [April 1, 2025, 6:55pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/3 "2025-04-01T18:55:16Z")

</div>

We are also having the same issue after upgrading to React 19.

zoomus-websdk-zoommtgMain.umd.min.js:2 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘ReactCurrentBatchConfig’)

---

<div class="post-metadata">

**Author:** ![robal](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/robal/32/68566_2.png) [@robal](https://devforum.zoom.us/u/robal)\
**Post date:** [April 15, 2025, 8:44am UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/4 "2025-04-15T08:44:43Z")

</div>

i am having same issue

---

<div class="post-metadata">

**Author:** ![matthewfincher](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/matthewfincher/32/68638_2.png) [@matthewfincher](https://devforum.zoom.us/u/matthewfincher)\
**Post date:** [April 18, 2025, 6:07pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/5 "2025-04-18T18:07:43Z")

</div>

We have the same issue. Any update on this or at least a roadmap for React 19?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 18, 2025, 7:29pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/6 "2025-04-18T19:29:42Z")

</div>

Hi everyone  
Thanks for reporting this. Let me check internally and will get back to you

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 24, 2025, 2:45pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/7 "2025-04-24T14:45:08Z")

</div>

Hi everyone.  
I ran a couple of tests on my end and I was able to run our sample app with React 19  
Can you please try to replicate the issue you are seeing with our sample app

> **[GitHub - zoom/meetingsdk-react-sample: Use the Zoom Meeting SDK in React](https://github.com/zoom/meetingsdk-react-sample)**
>
> Use the Zoom Meeting SDK in React

---

<div class="post-metadata">

**Author:** ![JackYang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jackyang/32/1135_2.png) [@JackYang](https://devforum.zoom.us/u/JackYang)\
**Post date:** [April 24, 2025, 3:55pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/8 "2025-04-24T15:55:55Z")

</div>

[Comparing master...react19-test · zoom/meetingsdk-react-sample · GitHub](https://github.com/zoom/meetingsdk-react-sample/compare/react19-test) here is our test react 19 example.

 ![Screenshot2025_04_24_085536](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/f/5/f55c1e0b894db947b9162195732798e9cea819e5.jpeg)

if still issue. before we update to React 19. you can try

```auto
// This is a TEMPORARY workaround only!
if (!React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.ReactCurrentBatchConfig) {
  React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.ReactCurrentBatchConfig = { transition: 0 };
}

```

---

<div class="post-metadata">

**Author:** ![Rishav](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rishav/32/50924_2.png) [@Rishav](https://devforum.zoom.us/u/Rishav)\
**Post date:** [May 13, 2025, 11:41am UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/9 "2025-05-13T11:41:10Z")

</div>

Thanks for this temporary temporary workaround.

I wanted to clarify that I’ve already tried the temporary workaround,

```auto
// This is a TEMPORARY workaround only!
if (!React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.ReactCurrentBatchConfig) {
  React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.ReactCurrentBatchConfig = { transition: 0 };
}

```

However, **even with this workaround in place** , I’m encountering the another errors:

```auto
Uncaught TypeError: Iu is undefined
    at mc (zoomus-websdk-zoommtgMain.umd.min.js:2)
    ...

```

And also:

```auto
Uncaught Error: Minified React error #327; visit https://reactjs.org/docs/error-decoder.html?invariant=327 for the full message...

```

These appear to stem from the Zoom Web SDK bundle itself and seem to be related to React 19’s internal changes and how the SDK interacts with them.

Can someone from the Zoom engineering team confirm:

- Whether **React 19 and Next.js 15** are officially supported with SDK `3.13.1`?
- If not, is an update planned for compatibility?
- Is there a stable workaround that doesn’t rely on internal React fields?

Appreciate any updates or guidance on this.

Thanks.

---

<div class="post-metadata">

**Author:** ![Sam14](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sam14/32/70042_2.png) [@Sam14](https://devforum.zoom.us/u/Sam14)\
**Post date:** [July 3, 2025, 5:25pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/10 "2025-07-03T17:25:28Z")

</div>

It is broken even in the sample. Things I did:

- Upgrade react and react-dom to 19.1.0.
- Change import to new Component view (line 3 of main.tsx to import from App-new)

Error:  
@zoom\_meetingsdk\_embedded.js?v=f4ee573c:20895 Uncaught TypeError: Cannot read properties of undefined (reading ‘ReactCurrentOwner’)  
at @zoom\_meetingsdk\_embedded.js?v=f4ee573c:20895:224  
at @zoom\_meetingsdk\_embedded.js?v=f4ee573c:2132:85  
at ../../node\_modules/.pnpm/@zoom+meetingsdk@3.13.2\_lodash@4.17.21\_react-dom@19.1.0\_react@19.1.0\_\_react-redux@8.1.2\_684fb7425fd808125c3b480dc3893f73/node\_modules/@zoom/meetingsdk/dist/zoomus-websdk-embedded.umd.min.js (@zoom\_meetingsdk\_embedded.js?v=f4ee573c:2133:6)  
at \_\_require2 (chunk-HDZN5KLF.js?v=f4ee573c:2135:50)  
at ../../node\_modules/.pnpm/@zoom+meetingsdk@3.13.2\_lodash@4.17.21\_react-dom@19.1.0\_react@19.1.0\_\_react-redux@8.1.2\_684fb7425fd808125c3b480dc3893f73/node\_modules/@zoom/meetingsdk/embedded.js (@zoom\_meetingsdk\_embedded.js?v=f4ee573c:42577:22)  
at \_\_require2 (chunk-HDZN5KLF.js?v=f4ee573c:2135:50)  
at @zoom\_meetingsdk\_embedded.js?v=f4ee573c:42580:16

Is there any planned upgrade to support React 19? Why is Zoom relying on React internals…

---

<div class="post-metadata">

**Author:** ![c\_rb](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/c_rb/32/72469_2.png) [@c\_rb](https://devforum.zoom.us/u/c_rb)\
**Post date:** [November 26, 2025, 4:45pm UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/11 "2025-11-26T16:45:32Z")

</div>

> Cannot read properties of undefined (reading ‘ReactCurrentOwner’)

I think this article articulates the problem pretty well: https:// blog.logrocket .com/why-third-party-integrations-break-react-19-how-future-proof/

---

<div class="post-metadata">

**Author:** ![Ben22](https://avatars.discourse-cdn.com/v4/letter/b/58956e/32.png) [@Ben22](https://devforum.zoom.us/u/Ben22)\
**Post date:** [February 17, 2026, 11:39am UTC](https://devforum.zoom.us/t/meeting-sdk-not-loading-the-meeting-with-react-19/127507/12 "2026-02-17T11:39:25Z")

</div>

Was anyone able to find a solution for this? We are still unable to upgrade to React 19 due to this.
