Bug: uppy.AddFile() cancels previous upload

[Aarbel]

Expected behavior

I want to allow my users to make parallelized uploads.
That means:

1. if a user goes on a page and uploads a big file TEST BIG FILE.mp4 (90 Mo)
2. then goes on an other page and uploads an other file TEST SMALL FILE.png (500 Ko) (but the big file isn't fully uploaded)
3. The two files will be uploaded

Bad behavior

Uppy instance keeps TEST BIG FILE.mp4in its state, but doesn't upload it. Only TEST SMALL FILE.png is uploaded.

At this step the Status Bar show that :

To reproduce

const uppy = Uppy({
	autoProceed: true,
	allowMultipleUploads: true,
	restrictions: {
        maxFileSize: TEN_GIGA_BYTES,
        maxNumberOfFiles: null,
        minNumberOfFiles: null,
        allowedFileTypes: null,
    });

uppy
  .use(AwsS3, {
	id: 'AwsS3',
    limit: 0,
	getUploadParameters: …
  })
  .on('upload-success', (file, response) => {
     console.log('upload-success File :', file);
  })
  .on('complete', (result) => {
	uppy.reset();
  })

let file
/* The file object will come from an input. Will be TEST BIG FILE.mp4 and TEST SMALL FILE.png.
   This function is triggered two times */
uppy.addFile({
	name: file.name,
    type: file.type,
    data: file,
    source: 'Local',
    isRemote: false,
})

Do you know how to fix it ?

[Aarbel]

Core problem is here:

Uppy seems to be fully cleaned when the TEST SMALL FILE.png has finished

[Aarbel]

Ok found the origin of the problem.

uppy.on('complete') 

is fired for each upload, so my reset() function was trigerred at the end of the second file upload.