-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Framework upload to Amazon's S3 failure #73
Comments
Hi, thanks for opening an issue. Does this problem only happen with Alamofire? It seems to be an issue with your S3 bucket. Do you have correct permissions & right credentials? Can you post your Romefile? |
All of the framework has a problem.I try to use the Romefile
|
Thanks I will look into it as soon as I am home. Other debug into that might be useful: Do you have Can you try a different bucket name? It might be just something stupid like the Just a tip: you don't need the entry in the repository map if the framework name follows the |
@bay2 It's definitely not the Also can you put your Alamofire at I believe this can still be a problem with your S3 permissions. You basically want IAM policies like this:
|
@bay2 I have tried with both environment variables and file credentials with a bucket named The bucket policy is the one I pasted above. The ACL for my bucket is Read/Write for If you have any more that you can share I'll be happy to try to replicate again on my side. |
@bay2 do you mind it I try with those? |
Oh, my S3 configuration problem.Thank you for your help. |
@blender Now I uploaded successfully,Thanks |
@bay2 Great! Can you share your config? Is it any different from what I suggested? |
I created a bucket in the ap-southeast-1 (Singapore) is uploaded successfully. |
Enhancement Suggestion
output:
The text was updated successfully, but these errors were encountered: