Closed dmost714 closed 2 years ago
Hi @dmost714 👋 thanks for raising this issue. It seems this behavior might be particular to multipart/resumable file uploads. Looks like we've already identified this to be a bug and is a duplicate of #8781. I'll reach to the team and see if there are any updates on this issue.
I'd be surprised if they're not related. That said, I am able to reproduce this with a 588 byte file and async/await, so this may be broader than multipart and resumable.
Hi @dmost714, this should be fixed by #9587 and available on 4.3.18
I tested my code w/ network OFF and verified I could still reproduce the bug. I updated to "aws-amplify": "^4.3.18", re-tested and can confirm the bug is fixed.
Thank you!
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels or Discussions for those types of questions.
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Storage
Amplify Categories
storage
Environment information
Describe the bug
The Storage.put() api does not fail when there is no network connection.
Expected behavior
If the API is unable to successfully upload the file it should throw an error or call the error callback.
Reproduction steps
Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
This issue may be related: Storage.put of multipart file returns successfully upon failure