-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
StorageReference.putFile completion never called (if file errors) #2350
Comments
Note: The same issue happens when the file ULR points to an empty file. |
BTW, I am not sure if uploading an empty file makes sense here... @ryanwilson @schmidt-sebastian, Do you think it does? It looks like we can throw a validation error in case of the empty file as well, then the issue can be closed by a single PR in the Firebase repo, so |
I don't think we should reject empty files. After all, this API is going to be user with user-provided files and we should handle all file sizes gracefully for our developers. Supporting empty files is certainly not a high priority but we should support it in the long term. |
* FIRStorageUploadTask: validate data and fileURL before upload (#2350) * FIRStorageReferenceTests: Verify a specific error (#2350) * Code cleanup. More informative error. * FIRStorageReference: error message, test fix (#2350) * Run ./scripts/style.sh * #2350: Punctuation * FIRStorageReferenceTests: naming (#2350) * Run ./scripts/style.sh * Tests fixed (#2350) * FIRStorageReferenceTests fixed for Mac OS (#2350) * FIRStorageUploadTask: validate content just before uploading (#2350)
Is anyone facing the same problem even when the file is not empty (an image in my case) |
@Black-riddle your Firebase looks a bit old. Would it be possible to test your issue with Firebase |
@maksymmalyhin Thank you now it works :) |
The issue should be completely fixed by the fix of google/gtm-session-fetcher#140 |
When using
StorageReference.putFile
errors such as "no such file" gets silenced and the completion block is never called.Relevant Code/Steps to reproduce
At first glance it seems like #1888 is related, but there it seemed like people had troubles uploading existing files as well.
The text was updated successfully, but these errors were encountered: