I've built SyncEvolution 18.104.22.168 for Harmattan, and put it up on
as before. I've tried to add a
simple Aegis manifest file that requests access to the calendar and
Since I now have a N950 (thanks for the support, Roman), I've managed to
run some simple tests. After I added the Aegis manifest, it no longer
seems to hang when trying to access the contact database. Not sure if
Roman's alarm thing is also fixed, since I didn't see that problem myself.
However, there's still some problems...
Patrick, what do you make of this "permanent" contact?
~ $ syncevolution --export - goosync addressbook 874
This empty "contact" seems to be permanent, possibly an artifact of the
database itself. It was there from the start (the database was otherwise
empty), and is not visible in the Contacts UI. It cannot be deleted.
This causes a refresh-from-server to fail (and maybe hang for some
reason later on), like this:
[INFO] addressbook: deleting <874>
[ERROR] addressbook: error code from SyncEvolution fatal error (local,
status 10500): addressbook: remove contact: failed with error 7, entry
#0 failed with error 7
For comparison, a "real" entry:
~ $ syncevolution --export - goosync addressbook 101810
Since you presumably wrote the QtContacts backend, any ideas on where
that dummy contact might come from, and how to suppress it, so that
refresh-from-server could be made to work (and slow syncs won't transmit
an empty contact all the time)?