-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught Error: Cannot have two MultiBackends at the same time. #162
Comments
I'm experiencing the same error, stacktrace:
This is after upgrading |
@nomcopter Any development on this issue in the past 6 months? |
@gjvoosten Did you ever find a solution here? |
@mfranzs No. We're still on 3.2.0. |
Same issue here |
Appears to go away when disabling React script mode |
In case it's useful to reproduce, I hit this with React Router, navigating between two components on the same page that had different Mosaic instances. Not rendering Mosaic until each component has fully mounted seems to avoid this |
Have you tried using |
@nomcopter Well, what do you know? Your suggested work-around actually works for me. I found a reproducible scenario, and after replacing |
@gjvoosten any clues as to which versions of those libraries are working? I'm currently attempting:
and hitting the "Could not find the drag and drop manager" error. |
@alex-r-bigelow We only have a direct dependency on
No We're using React 18.2.0. |
Thanks; after fighting this for a few days, ended up just importing the version that installs with Mosaic, without adding it (or index.tsx
index.d.ts
|
Hello, my application which uses this library randomly crashes with error:
Uncaught Error: Cannot have two MultiBackends at the same time.
Full stack trace:
Right above also these errors appear multiple times :
I don't know if this could be error in my code, but I have only one instance of Mosaic component and the error appears randomly. Sometimes when I add or remove MosaicWindow, sometimes right after page refresh and sometimes when I am not doing anything. But it is usually quite rare, only seems to appear more often after dev server hot reload.
Do you know what could be the cause of this?
Thank you for your help.
The text was updated successfully, but these errors were encountered: