View Single Post
Old 01-27-2017, 11:48 PM   #13
Steve_Haley
CC iOS Developer
Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.
 
Posts: 142
Karma: 53024
Join Date: Jul 2012
Location: England
Device: Variety phones/tablets
Quote:
Originally Posted by gjohn4317 View Post
[Discussion about book size]

Steve, I tried sorting all books by size, then loading only those that were less than about 4 MB. a few books were 30 or 40 MB, so I thought perhaps somehow they were "kicking" something off. No joy - when I had transferred approx. 2900 books, CC closed immediately, no black screen, no reverting to initial welcome page.
I wish I could figure out why your database was coming out as being so large. I've got 4,000 books, and the entire folder, including the books themselves, is less than 1gb. The database in CC doesn't store the files, just the metadata, so it shouldn't be anywhere near as large as the overall folder.

Unfortunately I don't have anything great to suggest. All I can think of is just trying to keep a smaller library on CC for now. As written above, it's not the size of the book itself which matters, but rather what metadata is associated with the book. The metadata contains things like the authors, tags, custom columns, cover image and comments. Only the cover image and comments really should have the potential of getting large, but not usually under normal use. (I've heard stories of people storing the text of the book in the comments, which would certainly cause issues with making the metadata massive. Is this something you're doing? Unlikely, I realise...)

Quote:
Can you send me the previous version app and instructions on how to load it? I could use that right away.
Apple makes it hard to do this kind of thing since they want people to use the App Store exclusively. I can't even revert the changes and publish a new version since this update is actually working better for most people. The number of crashes has gone down overall.

My current plan is to spend some time over the next couple of weeks rewriting part of the transfer and databasing process. This is where the crash is happening for you, and I assume it's the same place for others. We'll have to see how it goes after that update.

If I could just refund your order, I would; at least then you wouldn't feel tied to making this work.
Steve_Haley is offline   Reply With Quote