Bad Request error with _context.LoadAsync about aws-sdk-unity HOT 6 CLOSED

@MHopke : a couple of things might be causing this issue:

1. Make sure you have created the DynamoDB table in AWS Console first with the selected hash key
2. LoadAsync is a generic method and takes the client-side class mapped to the table created in step 1.

from aws-sdk-unity.

EDIT: I did find the overriden method that takes a range key, but I am still receiving the WebException 400 : badrequest error. Additionally, the application throws an additional error when using System.Enum.Parse on the badrequest value.

Thanks for getting back to me! I do have the table set-up, although it has both a hash and range key, could this be causing the issue? (And I do have the class mapped to the table)

from aws-sdk-unity.

easiest way to debug bad request error is to enable this flag.

AmazonLogging.EnableSDKLogging = true;

before making any request. Check the logs for the curl command, try running the curl command using terminal( or cygwin if you are using windows).
I am guessing there's something missed between the declared hash & range key and mapped classed.

from aws-sdk-unity.

Ok thank you! I will give that a go tomorrow.

On Saturday, December 20, 2014, Kalyanaraman Santhanam <
[email protected]> wrote:

easiest way to debug bad request error is to enable this flag.

AmazonLogging.EnableSDKLogging = true;

before making any request. Check the logs for the curl command, try
running the curl command using terminal( or cygwin if you are using
windows).
I am guessing there's something missed between the declared hash & range
key and mapped classed.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Michael Hopke
Partner & Senior Programmer | gametheory

from aws-sdk-unity.

Thanks for all the help! The user role was denying Describe table permissions, which was causing the error.

from aws-sdk-unity.

great ! please mark this issue as closed

from aws-sdk-unity.