Error when syncing via iCloud: “record to insert already exists”

A place to discuss Bookends for iPad, iPhone, and iPod touch.
Post Reply
propofol
Posts: 13
Joined: Wed Jul 15, 2015 2:55 pm

Error when syncing via iCloud: “record to insert already exists”

Post by propofol » Thu Oct 10, 2019 12:11 pm

Hello, after months of no-problem usage, I ran into an iCloud sync issue recently where I get the error message: “Error saving record to server, record to insert already exists.”

I am given the option of continuing or suspending.

Is there a way to fix this?

Thanks!

Phil

Serge
Posts: 213
Joined: Sat Oct 22, 2011 1:09 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by Serge » Thu Oct 10, 2019 2:20 pm

Please send a screenshot of the error message to support@referencesontap.com.
And try to resync your library:
1. Tap on the gear icon in the Sync row.
2. “Unlink this library from cloud…”
3. Sync with your existing library in the cloud.

propofol
Posts: 13
Joined: Wed Jul 15, 2015 2:55 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by propofol » Thu Oct 10, 2019 5:10 pm

Thank you.

Screenshot sent.

I did as instructed and the same error came up.

albiracer
Posts: 10
Joined: Tue Jan 02, 2018 3:17 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by albiracer » Sun Oct 13, 2019 6:13 pm

I’m having the exact same error. Tried the fixes suggested and didn’t work for me either. Fwiw, this is first time I’ve opened bookends iOS since upgrading to iOS 13 today.

albiracer
Posts: 10
Joined: Tue Jan 02, 2018 3:17 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by albiracer » Mon Oct 14, 2019 4:42 pm

Following up on this, forgot to ask: should I send screenshot to the support email as well?

Serge
Posts: 213
Joined: Sat Oct 22, 2011 1:09 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by Serge » Tue Oct 15, 2019 10:21 am

Yes, please send a screenshot and your library file on the Mac. Since resync didn't work it looks like the only option is deleting your library on iOS and downloading a new one from the cloud. Or download from the cloud to a different name, check to make sure it's OK, then delete the old library.

fmeres
Posts: 11
Joined: Sun Apr 14, 2019 1:23 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by fmeres » Mon Oct 21, 2019 9:19 am

I'm having the same issue since upgrading to iOS 13. I also noticed that a number of groups with long numerial names were automatically created. I'll send a screenshot to the support email.

aroddick
Posts: 23
Joined: Tue Aug 29, 2017 1:27 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by aroddick » Mon Oct 21, 2019 7:00 pm

I’m having this issue and the “atomic” issue. Re-sync doesn’t seem to resolve anything on my end.

Serge
Posts: 213
Joined: Sat Oct 22, 2011 1:09 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by Serge » Tue Oct 22, 2019 6:02 pm

The main problem with this cloud sync error is that we can’t reproduce it with our data, so it’s almost impossible to find the source of the problem. We will create a special build via TestFlight with which it will be possible to send the Bookends library from iOS to us via email. If you want to help with this please write to support@referencesontap.com. We will reply with instructions when we are ready.

Serge
Posts: 213
Joined: Sat Oct 22, 2011 1:09 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by Serge » Thu Oct 24, 2019 3:48 pm

It will be fixed in the next update. But the library should be redownloaded from the cloud (replacing the current library).

propofol
Posts: 13
Joined: Wed Jul 15, 2015 2:55 pm

Re: Error when syncing via iCloud: “record to insert already exists”

Post by propofol » Fri Oct 25, 2019 6:10 pm

Thank you for fixing this. I downloaded the latest Update and seems to be OK once the library has been deleted and then replace with the Cloud version.

Post Reply