View Single Post
Old 10-05-2020, 04:43 PM   #8
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by stumped View Post
The issue is not with moon per se, it's with Google android rules for how apps must share data.
I think , technically, the copy is created by cc when you tap read and moon is just told where to find it.
CC generates a content URI from the file when you click on "Read". See https://developer.android.com/refere...rovider#GetUri.

It is up to the receiving app how to handle that content. Moonreader does what is expected: it assumes a short-living permission and copies the stream to a file on its own, to be able to open it on the future.

If CC new company decides to hire a dev they can implement the last part of https://www.mobileread.com/forums/sh...30&postcount=6 in 10 minutes and move on (or give sound reasons if they consider it a bad idea). Until then CC users are suggested to rollback to 5.4.4.1 (or any version lower than that) or live with the read button making copies.
pazos is offline   Reply With Quote