I updated to Build 703 yesterday and made a new Kindle build of our app. When I installed it on the device I noticed that instead of a blurry icon I now just get a grey icon.
Did something change with regard to the naming convention for Kindle Icon files? [import]uid: 16734 topic_id: 18882 reply_id: 318882[/import]
Did you try building one of the sample apps to see if the Icon was correct? Maybe something changed in your own app. Build 703 was tested on the Kindle and the Icons were fine.
The blurry icon is normal on the Kindle when you are installing local apps. When you submit to the Amazon store, you upload a 512x512 Icon, which is used to create the Icon users see when they download and run your app. [import]uid: 7559 topic_id: 18882 reply_id: 72928[/import]
Tom,
There are only two differences in my build assets compared to when it worked:
I doubt #1 would cause the problem, but perhaps #2 is an issue.
I’ll try building two versions on your sample; one with the existing icon and one with that same icon modified to add some transparent pixels. I’ll let you know what I find.
[edit] The Ansca sample build fine and shows the blurry Ansca icon on the bookshelf. I rebuilt my app and it still shows the large grey square in place of my icon. However, when I was using AndroExplorer to install it, that app correctly shows my icon in the upper left corner prior to installation.
Next I will try removing the other Icon file I added and see if that fixes it.
[edit] It appears that if you have an alpha channel in your Icon.png this doesn’t always work on the Kindle. I removed the alpha from Icon.png and it now works.
However, I still have rounded corners even though I replaced the alpha with black. Since the Android based devices are supposed to use the Icon-hdpi.png, Icon-mdpi.png, and Icon-ldpi.png I have no idea why changing my Icon.png file would cause this to work. I tried removing the Icon.png before making my build, but the log window complained that the file wasn’t found so I added it back.
NOTE: The Ansca Icon.png has no alpha, but the Icon-?dpi.png files do and your Icon has transparency on the Kindle.
Given all of the above, it appears that somehow Ansca is using the Icon.png to “decide” if an icon is present, but then using the Icon-?dpi.png files for the device. If the device (Kindle in this case) uses Icon-?dpi.png, then please do NOT base anything on the existence of the Icon.png file or whether or not that file has transparency.
This is definitely a bug, but since it can be worked around fairly easily I suspect it will be given a low priority. [import]uid: 16734 topic_id: 18882 reply_id: 72931[/import]
Any news on that? [import]uid: 142895 topic_id: 18882 reply_id: 119667[/import]
I haven’t touched the Kindle in a number of months. There just weren’t any sales to justify it. [import]uid: 16734 topic_id: 18882 reply_id: 119684[/import]
I have been meaning from CoronaLabs the update 
But you had bad sales or no sales? [import]uid: 142895 topic_id: 18882 reply_id: 119686[/import]
We had good sales on the Nook, decent sales on iOS and almost zero sales on the Kindle. [import]uid: 16734 topic_id: 18882 reply_id: 119688[/import]
Any news on that? [import]uid: 142895 topic_id: 18882 reply_id: 119667[/import]
I haven’t touched the Kindle in a number of months. There just weren’t any sales to justify it. [import]uid: 16734 topic_id: 18882 reply_id: 119684[/import]
I have been meaning from CoronaLabs the update
But you had bad sales or no sales? [import]uid: 142895 topic_id: 18882 reply_id: 119686[/import]
We had good sales on the Nook, decent sales on iOS and almost zero sales on the Kindle. [import]uid: 16734 topic_id: 18882 reply_id: 119688[/import]