Calibre Sync broken by Calibre v9?

[GeniusJ]

Originally Posted by ReadingEnjoyer

I emailed the developer of Calibre Sync. I hope he will fix it soon. The last update on Android was in April 2025. There is as far as I can tell, no alternative. I purchased Calibre Sync awhile ago and have relied on it extensively. I'm surprised it is the only program like it.

It's not the only program like it. A few messages back in this thread, someone pointed out Calibre View (although it won't read my Dropbox account correctly, so I can't properly test it).

[jbusnengo]

Originally Posted by GeniusJ

It's not the only program like it. A few messages back in this thread, someone pointed out Calibre View (although it won't read my Dropbox account correctly, so I can't properly test it).

That doesn't help those of us with Android devices.

[ReadingEnjoyer]

Originally Posted by jbusnengo

That doesn't help those of us with Android devices.

I use android. I found the original developer by name and emailed him too. He replied saying he no longer has any involvement. This doesn't seem like a good sign. I still haven't received a reply from the official developer email.

calibre.sync.help@gmail.com is their official support email.

[GeniusJ]

I posted a Windows Powershell script which fixes it for me. It adds the 3 columns back to the db file, and only needs to be run once after every time Calibre updates and drops the tables again. Just quit Calibre, run the powershell, and viola the columns are back until the next time Calibre updates. My post is in another thread about this.

[PeterT]

Originally Posted by GeniusJ

I posted a Windows Powershell script which fixes it for me. It adds the 3 columns back to the db file, and only needs to be run once after every time Calibre updates and drops the tables again. Just quit Calibre, run the powershell, and viola the columns are back until the next time Calibre updates. My post is in another thread about this.

calibre will NOT drop the columns on each upgrade. The DB updates are based on the USER_VERSION stored in the database. If the upgrade contains a newer version than the actual database the required code is run once and the database USER_VERSION updated to reflect that change.

[GeniusJ]

Oh cool, then in that case it sounds like maybe the script only needs to be updated once. I like one and done.

[VelvetElvis]

Originally Posted by ReadingEnjoyer

I still haven't received a reply from the official developer email.

calibre.sync.help@gmail.com is their official support email.

I emailed him right after the issue came up, and provided information on the fields in question. No response. Mailed him again Saturday, and said if he's not going to fix it, then he should at least pull it from The Play Store so people won't get burned buying a broken app. Of course, no response to that either.

[xyris]

Originally Posted by GeniusJ

I posted a Windows Powershell script which fixes it for me. It adds the 3 columns back to the db file, and only needs to be run once after every time Calibre updates and drops the tables again. Just quit Calibre, run the powershell, and viola the columns are back until the next time Calibre updates. My post is in another thread about this.

Sorry if this is a stupid question, but WHERE did you post your PowerShell script? I'd like to try it, if you allow.

Alternatively, could someone post instructions for the computer-adventurous like me, who are willing to learn, but need guidance with such technical stuff like editing metadata.db to restore CS functionality?

Thanks a lot!

[DNSB]

Originally Posted by xyris

Sorry if this is a stupid question, but WHERE did you post your PowerShell script? I'd like to try it, if you allow.

Check message #328 in the Calibre Sync for Android & iOS thread.