Bug 404438 - modify an item => //schemas.google.com/g/2005#home:x@y.z instead of x@y.z
Summary: modify an item => //schemas.google.com/g/2005#home:x@y.z instead of x@y.z
Status: RESOLVED DUPLICATE of bug 398847
Alias: None
Product: libkgapi
Classification: Frameworks and Libraries
Component: contacts (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-16 12:30 UTC by Philippe ROUBACH
Modified: 2019-02-24 19:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2019-02-16 12:30:59 UTC 
SUMMARY
if in a contact in kaddressbook i change one item phone number for example then mail address  x@y.z is changed to //schemas.google.com/g/2005#home:x@y.z

STEPS TO REPRODUCE
1. go to a contact in kaddressbook
2. change phone number or photo or name display
3. sync kaddressbook and google contacts

OBSERVED RESULT

x@y.z is changed to //schemas.google.com/g/2005#home:x@y.z

EXPECTED RESULT

mail stays x@y.z

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1

ADDITIONAL INFORMATION

kontact 5.10.2
Comment 1 Philippe ROUBACH 2019-02-16 12:39:08 UTC 
libkagapi 18.12.2
Comment 2 Philippe ROUBACH 2019-02-16 12:50:01 UTC 
more

if i change mail adress to x@y.z 
then
at next sync mail adress becomes again //schemas.google.com/g/2005#home:x@y.z

note : google side mail adress is correct !
Comment 3 Philippe ROUBACH 2019-02-20 11:53:20 UTC 
worse !

at each modification about a contact #home://schemas.google.com/g/2005
is added in email field

for a contact i get this after 4 mofifications

//schemas.google.com/g/2005#home://schemas.google.com/g/2005#home://schemas.google.com/g/2005#home://schemas.google.com/g/2005#home:x@y.z
Comment 4 Colin J Thomson 2019-02-24 19:56:25 UTC 

*** This bug has been marked as a duplicate of bug 398847 ***