Parceler | 简单的Bundle数据注入框架 | Web Framework library

I experienced this exact same problem today, and was able to solve. Turns out the issue was a version mismatch between the expected version of androidx.lifecycle:lifecycle-viewmodel used by the module where the "failing" class is and a later version in some other dependent code.

So in my case, my module was using version 2.1.0 of this module, but one of the dependencies was using version 2.2.0. The code will compile no problem, because gradle resolves the dependency to the latest version; however Android Studio is somehow confused by this situation (not always, because this doesn't happen all the time, but sometimes – this isn't the first time I've seen this.)

Therefore solution is: figure out what the latest version of this library is in your app and update your build.gradle for this module to point to the same version that gradle is resolving to. Or:

1. run gradlew app:dependencies
2. search the result for lifecycle-viewmodel
3. update build.gradle in your app to depend on lifecycle-viewmodel with the version that gradle says it is resolving to
4. Sync project with gradle files

Since you are developing using Android Studio 3.1.3, try to update your build.gradle dependencies and plugin as well to their latest version.

And move your repository google() to the buildscript.

You can try this:

Top-level build.gradle

I'd recommend taking a look at the @Parcelize annotation provided with the Kotlin Android Extensions, it generates all necessary boilerplate for you so you don't have to write and maintain that code yourself.

So, turns out this issue was due to mismatch between play services/support library versions my app was depending on directly and transitive dependences from FirebaseUI - https://github.com/firebase/FirebaseUI-Android#upgrading-dependencies

Your error that is causing your build to fail is here:

It's a bug on the Parcelize plugin like you mentioned https://youtrack.jetbrains.com/issue/KT-19853 and it can be solved by either reflection or actually, you can have a proxy class to java as you can access that CREATOR field in java without any problems.

I made a util java class for all creators and then made a kotlin extension referring to that creator

Java

Thanks to @EpicPandaForce. I am able to resolve this error by importing proxy classes as following way.

Changing the version of Parceler library from 1.0.4 to 1.1.10 solved the problem. I don't know what is the reason behind this but I guess it may be because of some transitive dependencies using version 1.1.10

When minify is true then also proguard is used which rewrites names. To keep it in original version add it to proguard.cfg files, example: