Export for Amazon Error

I successfully created and uploaded an app to Google for Android so I feel like my code is correct. I used these guidelines to prepare it for export:

http://docs.coronalabs.com/guide/distribution/kindleBuild/index.html

When I go to build one for Amazon for the Kindle, it comes up with the following:

A device build error occurred on the server. 

BuildID: 52addb286b17c 

Error:  

Does anyone know what might be causing this, what this means or where I might start looking to troubleshoot it?
 

Thank you!

What messages are in your console log?

What is your build.setting look like?

What version of Corona SDK are you using?

Im not sure how to access the console log but the error message that came up was in the original post.

Build Settings are:

settings = { orientation = { default = "portrait", supported = { "portrait", "portraitUpsideDown", "landscapeLeft", "landscapeRight" } }, android = { usesExpansionFile = true, usesPermissions = { "android.permission.INTERNET", "com.android.vending.CHECK\_LICENSE", "android.permission.WRITE\_EXTERNAL\_STORAGE" }, }, }

Corona SDK Version 2013.2076 (2013.07.15)

First, I would consider upgrading to build 2100.  It fixes quite a few things from 2076, though I don’t think it has anything to do with this issue.

For the log file:  Please read:

http://www.coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/

It will tell  you how to get information on what is going on.

Rob

What messages are in your console log?

What is your build.setting look like?

What version of Corona SDK are you using?

Im not sure how to access the console log but the error message that came up was in the original post.

Build Settings are:

settings = { orientation = { default = "portrait", supported = { "portrait", "portraitUpsideDown", "landscapeLeft", "landscapeRight" } }, android = { usesExpansionFile = true, usesPermissions = { "android.permission.INTERNET", "com.android.vending.CHECK\_LICENSE", "android.permission.WRITE\_EXTERNAL\_STORAGE" }, }, }

Corona SDK Version 2013.2076 (2013.07.15)

First, I would consider upgrading to build 2100.  It fixes quite a few things from 2076, though I don’t think it has anything to do with this issue.

For the log file:  Please read:

http://www.coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/

It will tell  you how to get information on what is going on.

Rob