Quote:
Originally Posted by stumped
I think that's a known issue . Chaley posted 18 months ago that the way CC hands of book files needs to be re-written for Android 7+ , unless this is another issue that needs attention
see here: post#2. https://www.mobileread.com/forums/sh...d.php?t=300234
based on performance to date by the new "devlopment team" for IOS there's little or no change of android work happening in time for a Nov 2020 fix. The app will probably just die or be kicked out of play store
its funny that when the "development team" was just Chaley , stuff got done.
the current team - size unknown - has achieved nothing praiseworthy in the last year
and the monthly excuses updates are wearing thin |
Nope, they're not the same issue. Chaley was talking about how file providers are left into the void in 7.1, so CC, as any other program, is not able to pass a File in a intent. That's not enforced on some vendors and still works for me on 8.1 in a Huawei tablet. In fact koreader does open files fine from CC and does not support VIEW intents that don't feed files.
The issue that I'm talking about is related with how CC, and any other program, sees the "shared storage" when building against API29+. It does need serious rework to be done.
CC won't be kicked out the Play Store. Just newer versions will require API29 on November 2020. If a new version is shipped before that date then it will work with API28 and CC will still work as intended.
So, any bugfix attempt, without changing the way CC handles the shared storage, needs to be done before scoped storage strikes in.
About the rest of your comments: they're exactly the reason most developers, with the help of app stores, delegate support forms to an email contact. I share with you the worry about the future of CC but bashing the people in charge won't help in any way.