Ticket #320 (closed defect: fixed)

Opened 8 years ago

Last modified 7 years ago

moto-sync overwrites e-mail address in phonebook after sync

Reported by: cschneemann Owned by: andrewb
Priority: normal Milestone:
Component: Plugin: others Version: 0.20
Severity: normal Keywords:
Cc:

Description

reproduction:

  1. add an emailaddress to an contact in the phonebook (mobilephone) (you will get an second entry with the emailadress)
  2. sync to kdepim (you will have one entry in the addressbook)
  3. sync again -> the second entry will be overwritten with the mobilenumber, the email is lost and you will have two entries with the same content

Change History

comment:1 Changed 8 years ago by cschneemann

ah, I forgot, motorola RAZR V3i

comment:2 Changed 8 years ago by andrewb

  • Owner changed from abaumann to andrewb
  • Status changed from new to assigned
  • Component changed from OpenSync to Plugin: others

Hmm, I think I might know what caused this. Contacts are expanded to occupy multiple positions when they are written to the phone, and collapsed again when read. The mapping of entry positions to UIDs is a pretty horrible hack (the phone doesn't have the ability to store UIDs, so we have to try to keep the phonebook position in the UID). I'm guessing that when the contact was written the second time, its positions were assigned in a different order.

Do you have the console output from the second sync run? I'd like to know what the UID of the event was, and see what moto-sync was writing to the phone (you'll have to manually censor the phone numbers and names etc., sorry about that).

comment:3 Changed 8 years ago by cstender

  • Version changed from 0.X to 0.20

comment:4 Changed 8 years ago by andrewb

  • Status changed from assigned to closed
  • Resolution set to fixed

I think this is fixed in revision 1348. Please try that and let me know.

There will still be a problem if the number of contacts for an entry changes (eg. you add another phone number). I don't have a good solution for this yet, but it's a known FIXME and should crash rather than overwrite data on the phone.

Note: See TracTickets for help on using tickets.