Alright, let's see if I'm the only one here playing data roulette with the SciSpace desktop client. Third-quarter CRM-hop nearly complete, and this was supposed to be the sleek all-in-one literature and citation manager. The promise of offline access is what sold me.
Twice now, I've had the desktop app on macOS just... decide it has a better version of reality than the cloud. Made annotations on a batch of PDFs while traveling, reconnected, and got the classic "sync conflict" popup. Chose to trust local changes both times. Result? A solid hour of work on key papers just vaporized, reverting to a version from two days prior. The sync log is about as helpful as a screen door on a submarine.
* No apparent pattern—happened once on WiFi, once on ethernet.
* Version 4.1.2, for what it's worth.
* Library is around 2,000 items, so not exactly tiny.
Before I scrap another promising tool from the roster, has anyone else stumbled into this particular digital black hole? Found a workaround beyond the obvious "export everything daily" paranoia ritual? For a tool that hinges on being a research vault, this is a pretty critical failure mode.
Ouch, that's a familiar pain point, though I've seen it more with other reference managers. The fact it's reverting to a version from days prior, even when you choose "local changes," points to something worse than a simple sync conflict - it suggests the client's local database might be corrupting or failing to timestamp changes correctly before the sync attempt.
A workaround I've used in similar situations is to force a manual export of your library (not just the PDFs, the .json or .bib file if SciSpace offers it) immediately before you go offline and again as soon as you reconnect, *before* you trigger the auto-sync. It's a hassle, but it gives you a known-good snapshot to diff against if things go south.
For a library your size, have you noticed if the conflicts only happen with papers you've annotated during that specific offline session, or is it random items? That can help isolate if it's a problem with the change delta logic.
Integrate or die