You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has caused many errors like «cannot read properies of undefined» in the wild. I think we should prevent events from being emitted after a file has been set to undefined.
See #3811
Event that sometimes get emitted with file argument undefined:
upload-error
upload-started
upload-progress
upload-success
preprocess-progress
preprocess-complete
postprocess-progress
postprocess-complete
dashboard:file-edit-complete
file-added
file-removed
So we need to search for all occurrences of each of these, and make sure that we don't emit an undefined file argument.
We haven't seen this happen anymore so the issue is not reproducible. Luckily we are migrating everything to TS, then we can make sure things are happening correctly.
This has caused many errors like «cannot read properies of undefined» in the wild. I think we should prevent events from being emitted after a file has been set to undefined.
See #3811
Event that sometimes get emitted with file argument
undefined
:upload-error
upload-started
upload-progress
upload-success
preprocess-progress
preprocess-complete
postprocess-progress
postprocess-complete
dashboard:file-edit-complete
file-added
file-removed
So we need to search for all occurrences of each of these, and make sure that we don't emit an undefined file argument.
For example here:
uppy/packages/@uppy/transloadit/src/index.js
Line 619 in 3121fae
we should probably return before emitting any events, or maybe better make sure files are only ever deleted after an upload has finished or failed.
The text was updated successfully, but these errors were encountered: