Hi Ismael,

see: https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html


JM


On 1 Feb 2020, at 18:18, Ismael Bouya <ismael@bouya.org> wrote:

Hi Ján,
Thanks a lot for this patch!
Are non-released code available somewhere? I didn’t see any repository
or so on the website.

Kind regards,

(Sat, Feb 01, 2020 at 06:14:31PM +0100) Ján Máté :
Hi Ismael,

this bug is already fixed in the latest relase candidates. Here is the fix:

https://www.inf-it.com/fixes/photo_attr_fix.diff <https://www.inf-it.com/fixes/photo_attr_fix.diff>


Cheers,

JM


On 1 Feb 2020, at 09:57, Ismael Bouya <ismael@bouya.org> wrote:

Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.

As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?

Kind regards,
--
Ismael


  Hi Ismael,
  this bug is already fixed in the latest relase candidates. Here is the
  fix:
  [1]https://www.inf-it.com/fixes/photo_attr_fix.diff
  Cheers,
  JM

    On 1 Feb 2020, at 09:57, Ismael Bouya <[2]ismael@bouya.org> wrote:
    Hello all,
    I’m using carddavmate and caldavzap for a long time, and I recently
    uncovered an issue:
    When I modify my contacts from infcloud, some of my pictures, the ones
    that get stored in png, have a field that looks like:
    -----
    PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
    -----
    when exported. It seems like this kind of formatting is not supported,
    so I guess it’s not a standard one: when synchronizing with other
    clients, like the stock android app or khard, they crash or are unable
    to display the picture.

    As soon as I remove the "data:image/png;base64," part of the field, it
    starts working again. Is it an issue with infcloud? Note that it used to
    work for a long time without any issue, and quite recently I
    simultaneously upgraded and migrated from caldavzap+carddavmate to
    infcloud. I’m not absolutely sure what changed, but maybe it will ring a
    bell to some of you?

    Kind regards,
    --
    Ismael

References

  Visible links
  1. https://www.inf-it.com/fixes/photo_attr_fix.diff
  2. mailto:ismael@bouya.org


--
Ismael