-
Notifications
You must be signed in to change notification settings - Fork 98
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
TypeError: Cannot read property 'destroy' of null #241
Comments
In the past, I was able to reproduce the issue as well. I guess some race condition occurs and this line in the watchdog feature fails https://github.com/ckeditor/ckeditor5/blob/f74de8bf3658506af756c311a3bdf0636799b1e1/packages/ckeditor5-watchdog/src/editorwatchdog.js#L82. cc: @ma2ciek |
Hi, @Sharvin26! Thanks for reporting this bug and for the described steps. I'll try to reproduce it and I'll check if it is easily fixable. |
I've been also trying with the browser navigation. |
Hello @ma2ciek, did you check the console? I am using Chrome Version 90.0.4430.212 (Official Build) (x86_64). |
Yes, not a single error in the console :/ |
@ckeditor/qa-team, could you test it as well? |
I could not reproduce this issue as well. @Sharvin26 Could you provide an example CRA project zip/github repo, where you are able to recreate this issue? |
I tried by creating a sandbox and it's working properly but facing the issue in my codebase. I cannot share the codebase though may be due to another package it's occurring ( not sure though ) |
We've received another report about this error and I think I've found a scenario of how to reproduce it in one of our implementations. Let's use our collaboration sample Steps to reproduce
Error
|
I also have this issue in CRUD actions. steps to produce: while deleting an index from array, the associated editor is causing the issue. I have tried to destroy using useeffect in unmount phase, but
|
I was also consistently running into this issue, adding a check before the |
Unfortunately, it may be a risky / leaky fix as the newly created editor will not be destroyed. I guess that a proper fix will need a small rewrite in the watchdog so the |
Is there a way to monkey-patch it / suppress the unhandled exception until an official fix comes out ? |
Connected thought would it be possible to use React |
This error caused the input to be stuck in production environment,I hope that can be resolved as soon as possible |
Could I ask you about checking the problem using the latest version of the |
Closing due to lack of activity. If you think the issue is still not resolved, please, re-open it and provide the feedback we asked for. |
Error:
I am getting the following error when using
ckeditor5-react
:Steps to reproduce:
npx create-react-app my-app
npm install --save @ckeditor/ckeditor5-react @ckeditor/ckeditor5-build-classic
When I open
http://localhost:3000
I do not see the above error but when I navigate to a page and navigate back then I see the following error in console.Versions:
I found this issue which is quite similar to what I am facing.
At the end it stats that issue has been resolved but I am still facing the same issue.
The text was updated successfully, but these errors were encountered: