aws_s3_upload
aws_s3_upload copied to clipboard
returns null without any exception
trying to upload a photo but response returns null without any exception. couldn't figure out why.
Future<String?> addPhotoToAws(File path) async {
String bucketName = "*****";
final response = await AwsS3.uploadFile(
accessKey: "*****",
secretKey: "******",
file: path,
bucket: bucketName,
region: "eu-central-1",
);
return response;
}
any idea?
@Serdnad i am getting 400 Bad request error when I debug the library. can you help?
did you find any solution for this? I'm having the same problem.
Same problem any solutions ?
Same problem any solutions ?
did you find any solution for this? I'm having the same problem.
unfortunately:( just decided to handle s3 logic in backend. this is how we solved the problem
@aligurelli try upgrade to the latest package version 1.5.0, I had a similar issue but it's resolved when I did upgrade the version to the latest
@aligurelli try upgrade to the latest package version 1.5.0, I had a similar issue but it's resolved when I did upgrade the version to the latest
thats a great news! but we already moved s3 handling to backend side. thank you for letting me now! if you are sure that problems has been fixed i can close the issue.
For me that was the fix, you can check it with your code if the problem is solved or not and also verify the ACCESS KEY and the SECRET KEY used
I'm getting the same issue where I don't get any error message and it the string returned is null. So can anyone suggest any solution for that?
Because this is null
https://github.com/Serdnad/aws_s3_upload/blob/master/lib/aws_s3_upload.dart#L113
if (res.statusCode == 204) return '$endpoint/$uploadKey';
only 204 returns result.
@Serdnad
are you still maintainance the project?
I'll occasionally review and merge PRs made against this repo, but most of my work these days isn't around Dart/Flutter, so it's admittedly not a very high priority for me. @shinriyo
That said, I did notice you just opened a PR, I'll take a look. Thanks!
I am having same problem. @Serdnad @shinriyo
Getting 400 Bad request.
Still, is there any official fix, I'm having the same problem.
Apr 6, 2023
same issue happened with me did you get any solution?
Same issue