-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replication status header wrong key #4284
Comments
Hi @ranielison thanks for sharing your issue. Can you clarify what error you are receiving and how this impacts your workflow? As a result of this key mismatch you are unable to download files using Amplify Storage targeting the copyTo bucket with files that were replicated in S3? Looking at our code, it seems the |
@fjnoyp I am using the downloadData method to download files and display them in my application. However, an error occurs during the download, as it throws the exception below. I made a copy of your package to my machine to reproduce the issue, and I modified the replication_status.dart file, changing the key from 'COMPLETE' to 'COMPLETED,' and it worked perfectly. E/flutter ( 4214): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Bad state: No element |
Good to hear @ranielison. We'll look into regenerating the smithy dart code or manually changing to |
This is resolved in amplify flutter 1.6.3. |
Description
Wrong key in the conversion of the replication status header to an enum. When downloading a file from AWS storage where the replication status is 'COMPLETED,' what is coming in the header status replication is 'COMPLETE' instead of 'COMPLETED,' causing an error in the application.
Categories
Steps to Reproduce
1 - Create a replication rule in your bucket to copy files to another bucket.
2 - Check the console to see if the replication status is COMPLETED.
3 - Try to download the file through your application.
Screenshots
No response
Platforms
Flutter Version
3.10.5
Amplify Flutter Version
1.6.1
Deployment Method
Amplify CLI
Schema
No response
The text was updated successfully, but these errors were encountered: