Closed ghost closed 5 years ago
GitMate.io thinks possibly related issues are https://github.com/nextcloud/contacts/issues/32 (Wrong assignment of fields while syncing contacts), https://github.com/nextcloud/contacts/issues/671 (Sync existing contact not working), https://github.com/nextcloud/contacts/issues/941 (iOS contact sync is wrong), https://github.com/nextcloud/contacts/issues/132 (Contacts not syncing from Android phone), and https://github.com/nextcloud/contacts/issues/480 (Contacts not readable in Opera).
What is the issue? When creating a contact, it does not push it to the server. Otherwise people would get empty contacts if they forget to edit them in the first place. As the tooltip says, change anything in this new contact and it will be synced to the server :)
@skjnldsv I did change things and the error persists.
I added a phone number and email and the error remained.
The only way to clear the error is to reload the page fully.
@a1pilot Sorry then, I did not understood your issue correctly! :) Can you post the content of your browser's log?
Console:
JQMIGRATE: Migrate is installed, version 1.4.0 contact.js:67 This contact did not have a proper uid. Setting a new one for t {jCal: Array(3), addressbook: {…}, vCard: t, conflict: false}
~~Nope, all is ok on those logs, when you edit the contact, there should be a little spinner.
Is it showing? Can you post a network log screenshot of the (supposed) contatc push request to the server? Before you do anything, still on the development tools, there is a tab called network
. Click on it and then the xhr filter. Do your action and screenshot the network log like this:
~~
EDIT: forget about this, I found the issue! Thanks @a1pilot !
@skjnldsv thanks. Not critical.
Version 3.0.5, when creating a new contact in the webapp it shows the following error:
Expected behavior Autosave should submit periodically.
Actual behavior Claims it isn't saving, but when moving to another contact the newly added one persists. Closing the browser and returning, the contact still exists. Appears to be an erroneous error.