media.show media PhotoLibrary broken on new Kindle Fire HD

Stephen_Lewis · February 6, 2013, 11:39pm

media.show media.PhotoLibrary is supposed to allow the ability to import images from the device’s library. This works on every device I tested it on: iOS, Nook, Nook HD, and the original Kindle Fire, but it FAILS on the newer Kindle Fire HD tablets.

This is easily reproduced by running Coronalabs’ sample app “PhotoPicker” on an actual Kindle Fire HD. It will fail to load an image picked from the library.

I have filed bug Case 20731.

I’m readying a cross-platform launch of my app (already available for Nook), and just discovered this problem while smoke-testing on a Kindle Fire HD 7. I hope it can be a quick fix. Thanks
-Stephen

[import]uid: 9422 topic_id: 35695 reply_id: 335695[/import]

Joshua_Quick · February 14, 2013, 7:39pm

Stephen,

This issue is now fixed. The fix will be made available in daily build #1030, tomorrow. [import]uid: 32256 topic_id: 35695 reply_id: 142825[/import]

Stephen_Lewis · February 14, 2013, 9:42pm

yea-haw!

Thanks, Joshua, I will stay up late to get the build

And now to hijack my own thread and ask if the other Kindle bug i entered , case # 20733, has any chance of being fixed, or even acknowledged as a bug. Specifically when I send an email with an image attached from a regular Kindle Fire (not HD) the image comes is viewed as garbage text in the receiving email client. Checking the email source reveals the content type “image” gets changed to “text”. I seem to remember this happening on the Nook Color a few months ago and you did something to fix it on that platform. FYI, it works as expected on the Kindle Fire HD.

-Stephen
[import]uid: 9422 topic_id: 35695 reply_id: 142829[/import]

Joshua_Quick · February 15, 2013, 1:36pm

Stephen,

I’ll have someone look into the e-mail attachment issue now. I remember it working for me on a 1st gen Kindle Fire when I tested it a year ago, so I’m curious as to what has changed. [import]uid: 32256 topic_id: 35695 reply_id: 142934[/import]

dchan · February 15, 2013, 1:50pm

Hi Stephen,
When I tested it on the Kindle Fire and the Kindle Fire HD the images showed up fine in the emails. Perhaps it has something to do with the email client that was used to send the email? There is also a known issue with images with names that have spaces in them. If that is the case then removing the space in the file name should do the trick. [import]uid: 223243 topic_id: 35695 reply_id: 142936[/import]

Stephen_Lewis · February 15, 2013, 4:56pm

Hi dchan,

This is what I see when I install and run the Coronalabs test app “ComposeEmailSMS” on a regular Kindle Fire (NOT HD):

Run app and press “compose Email” button
given options on how to send email I choose “send with Email”
The built in email app on Kindle Fire launches and I can see the images as attachments below the text portion of the message. I change the To to my email address, and press ‘send’.
On my email receiving client (Thunderbird on my iMac) I open the the received email. The attached images, “coronalogo.png” and “email.png” are interpreted as text and so show up as two large blocks of nonsense ASCII text below the main message.
If I view ‘message source’ of the email in Thunderbird I see that the Content-Type has been changed to “text/html” which explains why the image is being misinterpreted:

[html]
------ULSKIOJEVC01G9F3J03WVM6GRF0RSX
Content-Transfer-Encoding: base64
Content-Type: text/html;
name=“coronalogo.png”
Content-Disposition: attachment;
filename=“coronalogo.png”;
size=70315

iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAYAAABccqhmAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJ
bWFnZVJlYWR5ccllPAAAAyJpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdp
bj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6
eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMC1jMDYwIDYxLjEz…
[/html]

This is the same problem I am having with my own app. Also, your app and my own both work correctly on every other device and platform I have tested on, including Kindle Fire HD. Are you sure you are testing on a regular Kindle Fire? To be sure this isn’t something funky with my Kindle Fire I tried sending an email straight from the email app on the Kindle Fire (not going through a Corona app) from the same account to the same account, with. jpg and .png image attachments (some of which even had spaces in the name) and it was successful. On opening the email in Thunderbird the images came through as images. The message source shows “Content-Type: image/jpeg;”.

I feel like I have tested this every way I can to eliminate anything else that might be causing this. I still conclude that any email sent from a Corona app, from a regular Kindle Fire, with image attachments will convert the Content-Type to “text/html”.

Let me know if there’s anything else I can try, though. Thanks for taking a look.

BTW, I can verify that the KindleFire HD bug that started off this thread is fixed with the latest build, so thanks for that!

-Stephen [import]uid: 9422 topic_id: 35695 reply_id: 142962[/import]

Joshua_Quick · February 15, 2013, 8:50pm

Stephen,

I just tested our ComposeEmailSMS app on our 1st generation Kindle Fire too and my gmail web client received the image files just fine. I looked at the message source and I did notice that the “Content-Type” for the image files were set to “text/html” just like it did for you. That’s interesting. Perhaps gmail is much more tolerant of it? [import]uid: 32256 topic_id: 35695 reply_id: 142975[/import]

Joshua_Quick · February 15, 2013, 9:29pm

After doing some debugging, I’ve noticed that the Kindle Fire’s mail app is never fetching the MIME type from the mail attachments. I think I’ve found a solution to this, but it will require a lot of testing to make sure it doesn’t break our mail attachment support on any other device. We’ll work on this next week. Thanks for bringing this issue up. [import]uid: 32256 topic_id: 35695 reply_id: 142976[/import]

Stephen_Lewis · February 15, 2013, 9:42pm

Seriously, you guys are awesome. Thanks for tracking this down.

-Stephen [import]uid: 9422 topic_id: 35695 reply_id: 142978[/import]

Joshua_Quick · February 14, 2013, 7:39pm

Stephen,

This issue is now fixed. The fix will be made available in daily build #1030, tomorrow. [import]uid: 32256 topic_id: 35695 reply_id: 142825[/import]

Stephen_Lewis · February 14, 2013, 9:42pm

yea-haw!

Thanks, Joshua, I will stay up late to get the build

And now to hijack my own thread and ask if the other Kindle bug i entered , case # 20733, has any chance of being fixed, or even acknowledged as a bug. Specifically when I send an email with an image attached from a regular Kindle Fire (not HD) the image comes is viewed as garbage text in the receiving email client. Checking the email source reveals the content type “image” gets changed to “text”. I seem to remember this happening on the Nook Color a few months ago and you did something to fix it on that platform. FYI, it works as expected on the Kindle Fire HD.

-Stephen
[import]uid: 9422 topic_id: 35695 reply_id: 142829[/import]

Joshua_Quick · February 15, 2013, 1:36pm

Stephen,

I’ll have someone look into the e-mail attachment issue now. I remember it working for me on a 1st gen Kindle Fire when I tested it a year ago, so I’m curious as to what has changed. [import]uid: 32256 topic_id: 35695 reply_id: 142934[/import]

dchan · February 15, 2013, 1:50pm

Hi Stephen,
When I tested it on the Kindle Fire and the Kindle Fire HD the images showed up fine in the emails. Perhaps it has something to do with the email client that was used to send the email? There is also a known issue with images with names that have spaces in them. If that is the case then removing the space in the file name should do the trick. [import]uid: 223243 topic_id: 35695 reply_id: 142936[/import]

Stephen_Lewis · February 15, 2013, 4:56pm

Hi dchan,

This is what I see when I install and run the Coronalabs test app “ComposeEmailSMS” on a regular Kindle Fire (NOT HD):

Run app and press “compose Email” button
given options on how to send email I choose “send with Email”
The built in email app on Kindle Fire launches and I can see the images as attachments below the text portion of the message. I change the To to my email address, and press ‘send’.
On my email receiving client (Thunderbird on my iMac) I open the the received email. The attached images, “coronalogo.png” and “email.png” are interpreted as text and so show up as two large blocks of nonsense ASCII text below the main message.
If I view ‘message source’ of the email in Thunderbird I see that the Content-Type has been changed to “text/html” which explains why the image is being misinterpreted:

[html]
------ULSKIOJEVC01G9F3J03WVM6GRF0RSX
Content-Transfer-Encoding: base64
Content-Type: text/html;
name=“coronalogo.png”
Content-Disposition: attachment;
filename=“coronalogo.png”;
size=70315

iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAYAAABccqhmAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJ
bWFnZVJlYWR5ccllPAAAAyJpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdp
bj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6
eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMC1jMDYwIDYxLjEz…
[/html]

This is the same problem I am having with my own app. Also, your app and my own both work correctly on every other device and platform I have tested on, including Kindle Fire HD. Are you sure you are testing on a regular Kindle Fire? To be sure this isn’t something funky with my Kindle Fire I tried sending an email straight from the email app on the Kindle Fire (not going through a Corona app) from the same account to the same account, with. jpg and .png image attachments (some of which even had spaces in the name) and it was successful. On opening the email in Thunderbird the images came through as images. The message source shows “Content-Type: image/jpeg;”.

I feel like I have tested this every way I can to eliminate anything else that might be causing this. I still conclude that any email sent from a Corona app, from a regular Kindle Fire, with image attachments will convert the Content-Type to “text/html”.

Let me know if there’s anything else I can try, though. Thanks for taking a look.

BTW, I can verify that the KindleFire HD bug that started off this thread is fixed with the latest build, so thanks for that!

-Stephen [import]uid: 9422 topic_id: 35695 reply_id: 142962[/import]

Joshua_Quick · February 15, 2013, 8:50pm

Stephen,

I just tested our ComposeEmailSMS app on our 1st generation Kindle Fire too and my gmail web client received the image files just fine. I looked at the message source and I did notice that the “Content-Type” for the image files were set to “text/html” just like it did for you. That’s interesting. Perhaps gmail is much more tolerant of it? [import]uid: 32256 topic_id: 35695 reply_id: 142975[/import]

Joshua_Quick · February 15, 2013, 9:29pm

After doing some debugging, I’ve noticed that the Kindle Fire’s mail app is never fetching the MIME type from the mail attachments. I think I’ve found a solution to this, but it will require a lot of testing to make sure it doesn’t break our mail attachment support on any other device. We’ll work on this next week. Thanks for bringing this issue up. [import]uid: 32256 topic_id: 35695 reply_id: 142976[/import]

Stephen_Lewis · February 15, 2013, 9:42pm

Seriously, you guys are awesome. Thanks for tracking this down.

-Stephen [import]uid: 9422 topic_id: 35695 reply_id: 142978[/import]

Joshua_Quick · February 22, 2013, 9:55pm

Stephen,

The MIME type issue is now fixed. This fix will be made available in daily build #1035. If you can let us know if it works for you too, then that would be great! [import]uid: 32256 topic_id: 35695 reply_id: 143847[/import]

Stephen_Lewis · February 25, 2013, 9:22am

Hi Joshua,

The fix works in build 1035 works for me. I can now close my last bug for Kindle Fire and ship.

Thanks!

-Stephen [import]uid: 9422 topic_id: 35695 reply_id: 144155[/import]

Joshua_Quick · February 22, 2013, 9:55pm

Stephen,

The MIME type issue is now fixed. This fix will be made available in daily build #1035. If you can let us know if it works for you too, then that would be great! [import]uid: 32256 topic_id: 35695 reply_id: 143847[/import]