1

We are currently using filepicker.io's pickAndStore to allow users to upload multiple files (some small, some big) to a S3 bucket.

What happens to files that have completed upload after a user closes filepicker modal? On the javascript-client side the onError is passed a 101 error, but gives no information about completed files.

Are they removed by filepicker from our S3 bucket, or should we assume that there are stale files hanging around?

Thanks!

Tim McGowan
  • 13
  • 3

1 Answers1

1

I haven't found a solution to this issue yet either and it's causing orphaned files in our S3 bucket (that our app does not know about) which we need to clean up later.

How to reproduce the issue:

  1. Setup filepicker pickandstore to allow multiple file uploads.
  2. Upload 5 files.
  3. Let three complete.
  4. Close Filepicker window.

Issue: We never receive a partial JS callback for the three successes letting me know that three files are now sitting in my s3 bucket.

Two proposed solutions: 1. For multiple uploads, need a callback when all are complete/failed/window-was-closed with which arrays for which files were successful and which were failures. I like this option more. 2. Have a success/failure callback PER file?

Yuri Zapuchlak
  • 26
  • 1