Quote:
Originally Posted by stumped
ps a google search finds this ( undated) statement - even more confusing:
Note: CC Android no longer supports Google Drive. That support ended when Google stopped supporting the feature that CC uses to login to a cloud provider.
Related entries
Author:
Charles Haley
Revision:
1.0
You cannot comment on this entry
|
There should be a post after that one saying that I found a way around the problem.
Quote:
Originally Posted by stumped
update 2. I have rage quit the whole project. removed g drive backup and sync, removed the 3+Gb I put into g drive, reverted FFS to mirror only to dropbox
I need to feel 100% safe with now I manage calibre library and GOOGLE DRIVE IS NEVER GOING TO GET THAT TRUST BACK.
I may try with a 3rd cloud provider if one comes recommended for use with CC, but not if it means I have to get a microsoft account!
otherwise I will accept that my new tablet can only get books from the local PC when its on, and not from the cloud
I will keep dropbox going (, until they pull the plug on me,) as my main library backup. I have a spare library copy stashed to another external drive , just in case .
|
Too bad I wasn't faster. I suspect that the problem is related to the number of "items" in the library folder. Drive paginates the results if there are lots. How many is "lots"? I don't know, but it could be more than 1000.
However, the Drive API seems to order the results by default in reverse time order. If this is true then deleting and re-copying the metadata.db file should make the library visible by making the database the newest file in the folder.