My Build As Kindle Option Is Missing - Please Help

Daft Newbie question …

I have a new Pro subscription, but I only have the option to build for iOS or Android - no Kindle or Nook … am I missing the obvious - this is driving me nuts :frowning:

Cheers - Steve

Hey Steve,

Click Build for Android then in the Android Build setup window select

Target App Store > Amazon

This will work for you!  Tried and tested.

Thanks IcySpark

All the docs and videos were showing an extra ‘Kindle’ build option in addition to iOS and Android.  I guess that has now been removed ?

Anyway - I have made slight progress - before I was getting ‘your app is corrupted’ - now I am getting 'this application encountered a Lua error (see logs) or has been corrupted …

Cheers - Steve

Hi Steve, the move of the Nook/Amazon builds is new to one of the more recent daily builds.   We still have many people on the older daily builds and previous public builds.  The guides are more oriented at public builds than dailies.

Now for your error, you will need to be able to look at the devices console log to get more information on the error and see any debugging “print” statements you have added.  You will need to install the Android Debug Bridge tools and you will get a command line command (something you would use Terminal for) called

    adb logcat

With your device tethered, you run that command and it will dump the last bit of the console log and then run your app and watch for the error message to show up.  If you’re not command line friendly, an alternate tool called ddms is also installed that runs in more of a Windowed environment.  See the Debugging section of this guide:

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

Hey Steve,

Click Build for Android then in the Android Build setup window select

Target App Store > Amazon

This will work for you!  Tried and tested.

Thanks IcySpark

All the docs and videos were showing an extra ‘Kindle’ build option in addition to iOS and Android.  I guess that has now been removed ?

Anyway - I have made slight progress - before I was getting ‘your app is corrupted’ - now I am getting 'this application encountered a Lua error (see logs) or has been corrupted …

Cheers - Steve

Hi Steve, the move of the Nook/Amazon builds is new to one of the more recent daily builds.   We still have many people on the older daily builds and previous public builds.  The guides are more oriented at public builds than dailies.

Now for your error, you will need to be able to look at the devices console log to get more information on the error and see any debugging “print” statements you have added.  You will need to install the Android Debug Bridge tools and you will get a command line command (something you would use Terminal for) called

    adb logcat

With your device tethered, you run that command and it will dump the last bit of the console log and then run your app and watch for the error message to show up.  If you’re not command line friendly, an alternate tool called ddms is also installed that runs in more of a Windowed environment.  See the Debugging section of this guide:

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