-
Notifications
You must be signed in to change notification settings - Fork 272
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
ClassNotFoundException when putExtras on Implicit intent #367
Comments
Do you have proguard obfuscating class names? |
Yes i have add them, but, it is also happened on debug version which proguard disabled. |
Just realize this also happen on other custom that implement parcel object. So seems like it is not parceler bug ? |
Strange. It still sounds like an obfuscating problem. Can you view the classes in the apk? |
Same problem here using Parceler 1.1.12
|
Are you using Proguard? Also, verify the class names in your APK. |
This happens in debug builds without Proguard. It works well when using explicit intents. |
Can you come up with a quick demo app so I can debug? |
Hmmm, either that or the Parceler annotation processor isn't running. @doniwinata0309 @10erlosh could you share your build Parceler dependency statements? |
It turned out that my problem only occurs on a huawei device. As a workaround i wrapped the parcel with a bundle and put the bundle into the implicit intent:
I can live with that. |
Parceler version : 1.1.12
AGP: 3.3.1
Hi @johncarl81 , I got this runtime error on android system (the activity become crash, but it is crash on android application, and the intent not started. )
Turns out this is because i am starting intent chooser (implicit intent) and putExtra Parcelable, that was wrapped by my local object. here the example of code:
So the error seems to be happen when outside application (intent chooser) trying to unmarshalling the extra, which is wrapped using my internal component
MyParcelObject
.Do you know what might be wrong ?
Thank you.
The text was updated successfully, but these errors were encountered: