Zotero not syncing - Report ID 1924846177
I just switched from storing my PDF attachments on iCloud to storing them in Zotero storage as a way to support this excellent software. However, I am getting a sync error (which I think was present before I switched). I have filed a report (ID 1924846177) with the error messages, but the one that appears when I click the red exclamation point next to the sync arrow says "JSON.parse: expected ',' or '}' after property value in object at line 1 column 1207 of the JSON data"
Other error messages refer to a file file: "chrome://zotero/content/xpcom/sync/syncLocal.js" line: 670}, but I am unable to find this file on my computer. I typically use Safari rather than Chrome, but Chrome is installed.
Other error messages refer to a file file: "chrome://zotero/content/xpcom/sync/syncLocal.js" line: 670}, but I am unable to find this file on my computer. I typically use Safari rather than Chrome, but Chrome is installed.
return await Zotero.DB.valueQueryAsync("SELECT data FROM syncCache WHERE libraryID=? AND key=? AND version=? AND syncObjectTypeID IN (SELECT syncObjectTypeID FROM syncObjectTypes WHERE name=?)", [1, 'DMVT8U2F', 6199, 'item'])
Let me know if I just need to use one of the sync reset options or if its better to switch back to iCloud storage of attachments until a later date. I'm still happy to support Zotero.
This isn't related to file syncing. It looks like the item is from May 2020, and you would've started getting a sync error as soon as you modified it locally.
I'm not able to reproduce this in current versions, so it's possible the bug that caused it has been fixed since 2020. The easiest thing to do now is to duplicate the item, move over any child attachments or notes, select both items, and merge them, being sure to select the newer item. Then empty the trash and you should be able to sync.
JSON.parse: expected ',' or '}' after property value in object at line 1 column 1885 of the JSON data
I can't figure out how to reconfigure the query you gave me to track this one down. If you tell me how, then I'll try rooting out these bad entries.