Quote:
Originally Posted by kaufman
Very excited to start using this. How stable is it? Am I going to be reinstalling my library every couple of days?  |
One of the "lucky" things is that the library changes mostly affect the UI, permissions, and process control. There have been no changes in the DB code, and I don't expect to make any. In my testing I have had CC refuse to start, sometimes crash, and sometimes not work, but I haven't had a case where the DB was corrupted or the book files were damaged.
It is possible that something will go wrong with the permissions stuff and CC will fail to open a book folder, effectively making the books "missing". This has happened during testing. After fixing the problem so that the folder could be opened the books came back.
There is also the "minor" issue of Marshmallow's changes to Android's general permission structure. When running on Marshmallow CC checks on startup to ensure that it has permission to read/write device storage and dies if the user doesn't grant it. However, if a user revokes that permission while CC is running then "bad things" will happen, but I don't know what I can do about that.
Sometimes I wonder what Google is thinking. Trying to write apps where the permission environment can radically change while the app is running is ludicrous. They say that they didn't want to ask about permissions during install because "that is too much work", so instead they force every app to do it at runtime. Grrr...