Cannot open KMZ file as mail attachment although importing same KMZ works fine
Hi!
I'm looking for a solution where (technically unskilled) people can send positions/map markers from a desktop computer to smartphones. The easiest and fastest way to produce a map marker seems to be to create a placemark in Google Earth, right click on the placemark item and select "Email". So far so good. However, when I receive the mail on my phone (Galaxy S6) and choose to open the attached KMZ file in Locus Map I get an error saying "No points or tracks for the import in the file(s)". If I save the attached file and from inside Locus Map import the saved file the point imports successfully. Why can't Locus Map import the point(s) directly from the attachment? Sample KMZ file "Namnl.kmz" can be found in the attached zip file.
Cheers,
/Daniel
The same problem 
Good day Daniel,
this issue partially depend on email client you use in your device. Anyway generally to read an attachment directly from email client, it's needed quite dangerous Android permission: http://androidpermissions.com/permission/com.android.email.permission.READ_ATTACHMENT . Because I'm sure, that most of users do not need this feature, I do not plan extend Locus to correctly handle this for all email clients.
So if direct import do not work, recommended method is to save attachment locally and then import.
Hope my answer is clear.
Thanks for understanding.
Good day Daniel,
this issue partially depend on email client you use in your device. Anyway generally to read an attachment directly from email client, it's needed quite dangerous Android permission: http://androidpermissions.com/permission/com.android.email.permission.READ_ATTACHMENT . Because I'm sure, that most of users do not need this feature, I do not plan extend Locus to correctly handle this for all email clients.
So if direct import do not work, recommended method is to save attachment locally and then import.
Hope my answer is clear.
Thanks for understanding.
Hello,
Thank you for a very good explanation! I fully understand the implications if you were to require that dangerous Android permission. Furthermore I have now been able to verify a different behavior depending on which email client I use. The Gmail app seems to handle this better than the Samsung stock email client.
Thanks! :)
Hello,
Thank you for a very good explanation! I fully understand the implications if you were to require that dangerous Android permission. Furthermore I have now been able to verify a different behavior depending on which email client I use. The Gmail app seems to handle this better than the Samsung stock email client.
Thanks! :)
Replies have been locked on this page!