-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IllegalAccessException since AGP 7.0.2 everytime when Paper.book().read(key, defaultValue) is called after Paper.book().write(key, value) #188
Comments
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. |
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. |
I'm also experiencing this issue as described. |
class PaperTable --------> public class PaperTable |
@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 |
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:
And it doesn't allow to create instance into the Kryo library. |
Is this issue fixed now? |
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 |
Hey @pilgr,
first of all thanks for the great library!
But I found an issue which breaks my app after upgrading
'com.android.tools.build gradle
(agp) to7.0.2
. It is working with agp7.0.1
, so maybe it's not this library but one of the fixes of agp7.0.2
... See agp 7.0.2 changes especially Desugaring and reproducible buildsOr maybe even in the Kryo, kryo-serializers or objenesis libraries... Which actually are not up to date, which maybe causes the issue here. But I'am just guessing.. 😅
Steps to reproduce
-> App will crash with following stacktrace
If I can support to fix this issue just let me know or if any information is missing.
Best regards,
Josef
The text was updated successfully, but these errors were encountered: