Thanks for the debug log. Unfortunately what it shows is the worst I could imagine. Oreo on your device is refusing to honor fixed file path names, instead insisting that the damned Storage Access Framework (SAF) be used. Not all devices require this (mine don't), but enough seem to do so that I can't ignore it.
The consequence: to fix this I must update CC to respect the Nougat+ SAF rules that file paths cannot be used internally in an app and cannot be passed to other (reader) apps. Instead, CC must use SAF mechanisms, which means that CC must pass copies of books to reader apps instead of the original file name. I knew that Google has said I would need to do this by the end of the year in order to be permitted to update CC, but apparently I must deal with it now.
I am currently testing the changes. They are significant enough that I will run an alpha test cycle then beta test. I need to be sure that I haven't broken anything on pre-Nougat Android, that it works on Nougat/Oreo and higher, and that it works with a range of reader apps.
Sigh ...
|