IllegalAccessException since AGP 7.0.2 everytime when Paper.book().read(key, defaultValue) is called after Paper.book().write(key, value) about paper HOT 9 CLOSED

Thanks for very detailed report. It looks very weird and seems like an issue/limitation in AGP. Anyway I'll keep an eye on it.

from paper.

Hey, I'm having a similar issue starting from using AGP 7.0.2. Looks like R8 / ProGuard is removing some classes and causing errors.

from paper.

I'm also experiencing this issue as described.

from paper.

This still happens with AGP 7.0.3. Which contains following changes.

I also tried the sugessetd fix from @TJHello (thanks for that!) to make the class public but it doesn't work sadly.

from paper.

Is this issue fixed now?

from paper.

class PaperTable --------> public class PaperTable

from paper.

@pilgr can you prioritize this fix please? I can confirm it's still happening on 7.0.3 AGP version, 7.0.0 is OK though

from paper.

It looks like this is an R8 issue. If the -allowaccessmodification flag is present in proguard rules. It changes access of the default constructor to public, but keeps the class PaperTable internal:

# direct methods
.method public constructor <init>()V
    .registers 1

    .line 6
    .local p0, "this":Lio/paperdb/PaperTable;, "Lio/paperdb/PaperTable<TT;>;"
    invoke-direct {p0}, Ljava/lang/Object;-><init>()V

    .line 7
    return-void
.end method

And it doesn't allow to create instance into the Kryo library.
It helped me to make the default constructor private, this does not allow R8 to change access.
Making class public helped me also.

from paper.

Hey folks, sorry for keeping you waiting for the fix for such a long time. The good news – we have the new fixed version to try out. Please refer to this task for instructions and give your feedback #196

from paper.