Closed choyky closed 2 days ago
Proposed fix for the issue is submitted here: https://github.com/aws-amplify/amplify-ui/pull/6050
Hi @choyky thanks for filing this bug and for the proposed solution! I was able to replicate your bug in the latest version. I will bring up your PR with the team.
I've found that the suggested workaround using the legacy accessLevel field does indeed allow the modified File object to be uploaded. However, the key is set to the base file name in that case and path cannot be modified via identityId, so it does not completely address the issue.
Fix has been deployed @aws-amplify/ui-react-storage@3.4.1
Before creating a new issue, please confirm:
On which framework/platform are you having an issue?
React
Which UI component?
Storage
How is your app built?
Vite
What browsers are you seeing the problem on?
Firefox
Which region are you seeing the problem in?
No response
Please describe your bug.
FileUploader does not upload modified file content as described in documentation.
For example, in the following code snippet, file content is replaced entirely but FileUploader still uploads the original input file.
If the now deprecated
accessLevel
is used instead ofpath
as below, then the processed file content will be uploaded as expected.What's the expected behaviour?
FileUploader uploads processed/modified file contents instead of the original input.
Help us reproduce the bug!
You could use above example code to reproduce the bug. Check the file contents on S3 and verify that it is the same as original input.
Code Snippet
See above.
Console log output
No response
Additional information and screenshots
No response