Kaddressbook doesn't parse Google contacts correctly

I have searched around and haven’t anything about this. So posting here hoping someone can help. I’m running Kaddressbook 5.9.0 (App version 18.08). Kontact and Kmail are the same versions.

My contacts are showing this in the email fields:

Contact Name <//schemas.google.com/g/2005#home:#########@gmail.com>
:question:

If I edit the contact, it will just revert the next time it syncs. I’ve tried removing the addressbook and re-adding, clearing the Akonadi cache, I’ve tried akonadictl fsck. I’ve run out of ideas. Please is there anything else?

OH - running Leap 15, with KDE Plasma 5.13.5, Frameworks 5.49, QT 5.11.1

It is quite possible that you get a good answer here (after all there are quite a lot of KDE PIM users here), but maybe going to the KDE-PIM mailing list kdepim-users@kde.org might give you a still better audience.

Also the following could be interesting places:
https://forum.kde.org/
https://bugs.kde.org/

Thanks Henk. I’ll start posting and looking through the other sites.

No issues displaying google contacts within kaddressbook here.
Using the default for Leap 15 - kaddressbook 5.7.3 & Plasma 5.12.6

Yeah, i didn’t have issues with the previous version either. I found a couple of bug reports on the kde bug tracker that looked similar to my issue with the latest versions. I’ll report back any resolutions. But so far they haven’t posted any.

Just upgraded to kaddressbook 5.9.1 and the issue is still there. Started a bug with KDE (#398847 - link](https://bugs.kde.org/show_bug.cgi?id=398847)).

At least two other people are having the same issues. I’ve had two other people chime in with a mee too on the kde bug. One of them has tried with multiple versions and computers. It is still listed as reported.

I’m having the same problem with tumbleweed and kde 5.14.1, kontact version 5.9.2. For what it’s worth I have the same issue on another computer running debian unstable.

Gannicus - I started a KDE bug for this (link in previous post). I’ve had several people say they are also having the problem, and not just on Leap. So far I have not seen any comment or change in the ticket. It is still listed as reported.

Thanks for that update, Cybertaz. I hope the issue gets resolved soon.