readium / r2-lcp-kotlin Goto Github PK

Hi there,

can you please check, all built versions are built with errors and gradle cannot download from jitpack: https://jitpack.io/#readium/r2-lcp-kotlin

Error messages when opening/closing an LCP protected ebook (may be an application issue).

On Android 9

Steps:

• open an LCP protected epub; sometime the "Webpage not available page" appears. Swiping removes the message.
• close an LCP protected epub; the "Webpage not available page" appears.

Although it is stated as "active" on the frontend.
The function statusDocument() in LcpHttpService isn't able to fetch the status of the license and thus return a null value

I am using readium in Android but getting same below errorL

Failed to resolve: readium:liblcp:1.0.0
Show in Project Structure dialog
Affected Modules: r2-lcp
even i have added
maven { url 'https://jitpack.io' }

We're facing an issue while trying to use the classes from org.readium.r2.lcp.public (imported as a submodule). The build is failing with this error:

e: java.lang.IllegalStateException: failed to analyze: java.lang.IllegalStateException: processingEnv must not be null

https://stackoverflow.com/a/59530688

If we rename the public package in r2-lcp-kotlin, the error disappears.
The weird thing is that this problem doesn't occur in r2-testapp-kotlin. Do you have any insights into why @aferditamuriqi?

Regardless of this build error, I think the classes in public should be moved to the top-level package anyway.

The function areRightsValid() throws an exception when the current date is in the loan date range instead of allowing the user to import/open the book

Hi!

I noticed that the a publication is saved in the external storage in fetchPublication ( r2-lcp/src/main/java/org/readium/r2/lcp/license/License.kt). My thought is that internal storage is better because then the files are removed when the app is uninstalled. What are the benefits of storing publications on external storage?

Would it be possible to set the rootDir in the constructor, or should i just move the publication from external to internal after it is fetched?

We need a way to report the download progress of a protected publication to reading apps, because for large publications (e.g. audiobooks), it can take a long time.

In Swift it's implemented by returning an observable progress, but there might be a more idiomatic way to handle that in Kotlin. Maybe LiveData<Double>?