Dsyko
commented
3 years ago Some screenshots of the errors seen in console and error logger.
Open Dsyko opened 3 years ago
Dsyko
commented
3 years ago Some screenshots of the errors seen in console and error logger.
maryfs
commented
3 years ago @Dsyko are you able to reproduce it again on newest version? Or you just tried to back to older one , checked it leave as it is?
Dsyko
commented
3 years ago @Dsyko are you able to reproduce it again on newest version? Or you just tried to back to older one , checked it leave as it is?
@maryfs I was able to reproduce in version 3.22.1 which is what I was getting as of March 15 2021 when using the CDN link that requests the latest 3.x.x version. Has a new version been released since I reported this last night?
Right now in production we are pinned to version 3.21.1 to avoid this bug.
maryfs
commented
3 years ago @Dsyko the only way i can reproduce it with this error message is modifying file or deleting this file during upload. The problem is with browser, which lost access to file. Thats why i asked if you were able to reproduce it again.. it doesn't seem to be connected with lib version.
Dsyko
commented
3 years ago @maryfs Interesting, I am still able to reproduce reliably by changing back to version 3.22.1 I am uploading a large file (3+GB) but not doing anything to the file, like deleting or moving it.
maryfs
commented
3 years ago @Dsyko ok, our support will contact you with further steps.. I won't close this issue until we will resolve this. Thanks.
When attempting to upload a large file (2.8GB+) using the javascript API linked using
the code throws an error:
"DOMException: The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired."
When I roll back to version 3.21.1 this error goes away and large files upload successfully.
I assume it has to do with multipart uploads for larger files as I don't see the error when uploading small files.
Please please do more QA on your releases. We have a QA step in our releases to test uploads of larger files but this change in the Filestack JS package came between our releases so we did not have visibility on this issue until a large number of customers complained. We will be linking to specific Filestack versions in our releases from now on.