uppy | The next open source file uploader for web browsers dog | File Upload library

In the AWS S3 service in a single PUT operation, you can upload a single object up to 5 GB in size.

To upload > 5GB files to S3 you need to use the multipart upload S3 API, and also the AwsS3Multipart Uppy API.

Check your upload code to understand if you are using AWSS3Multipart correctly, setting the limit properly for example, in this case a limit between 5 and 15 is recommended.

it's cause you cannot save encrypted(bytes) to model

try this

This was discussed in this Flysystem AWS adapter github issue:

https://github.com/thephpleague/flysystem-aws-s3-v3/issues/284

A method is being added in Laravel, and will be released next Tuesday (February 22, 2022):

https://github.com/laravel/framework/pull/41079

Workaround

The Laravel FilesystemAdapter base class is macroable, which means you could do this in your AppServiceProvider:

Okay that was dumb. But yes, to read those error message for other npm newbs out there:

I am unable to run the repro you provided because it appears to require private API keys.

However, inspecting the code, here's what appears to be happening:

1. The component renders for the first time with reporting state as false. This causes the component to render, and a new instance of Uppy to be created by the effect within that component and stored in this instance of the 's state.
2. The user uploads a file, and hits the "continue" button, which sets reporting state to true. This causes the component to re-render, and show the component instead. The original component is unmounted, and the things that were present in its state, notably, the instance of Uppy that had the user's uploaded file, are lost.
3. The user hits the "Back To Photos" button, which sets reporting state back to false. A this causes a new instance of to render, and the effect that creates an instance of Uppy re-runs. The instance that is created is new as well, and thus won't show what it contained the last time it was rendered.

One way to solve this would be to lift up state that needs to remain the same as the is mounted and unmounted into the parent component. So the component would be responsible for creating the Uppy instance, and pass that as a prop to the .

See also this part of the Uppy docs:

Functional components are re-run on every render. This could lead to accidentally recreate a fresh Uppy instance every time, causing state to be reset and resources to be wasted.

The @uppy/react package provides a hook useUppy() that can manage an Uppy instance’s lifetime for you. It will be created when your component is first rendered, and destroyed when your component unmounts.

You could also re-factor your app in other ways if it feels like too much is happening in a single component. But the guiding principle would be: "don't create the uppy instance more than once in a single user flow".

Make sure you have latest version of the Uppy core & Uppy react NPM https://www.npmjs.com/package/uppy. After that pls initialize in this way

I don't think you need to map if you're just trying to find an item. You could do

Your return res.status(200).send({ "message": "Successfully uploadded the files" }) is too soon, it should be in the callback.

It could be problematic on large files since the beginning of the big file would be received and then the client already receives a response which could logically cut the connection in http