auto-value-parcel | An Android Parcelable extension for Google 's AutoValue | Android library

I don't know exactly how to solved it, but something similar happened to me and I managed to fix it by removing android studio completely and reinstalling.

remove from mac remove from windows

Robolectric may be the solution to your problem. It allows you to write unit tests in the test folder (note: not instrumented unit tests in the androidTest folder) that utilise a Context with access to all of your R.string.* resources.

Here is an example:

AutoValue: Parcel extension can't handle sets, but if you convert the property to a List things will work out of the box without a custom adapter. If you want to treat it as a Set you could do this. Keep in mind you'll probably also want to cache the Set.

In gradle plugin 3.0.0 and up the apt is no longer supported. use in-built annotation processor.

Retrolambda is not processing the Kotlin bytecode, and you should set the Kotlin compiler to specifically target 1.6 bytecode. This will not break anything in current version of Kotlin as it can generate the older bytecode for the same functionality.

annotationProcessor dependencies are not exported to other projects. Also these are not exported with libraries.

AutoValue itself works, because you defined it with a compile dependency. This is something you should not do either. So an better dependency setup would look like...

ProjectB

Fulfilling the ideal of Clear Architecture is a bit hard with Android, as Android is a entire framework that has its own specification, even at basic language level.

I think, as the ideal of specific tools free level is mostly for testing purposes, thus - this should be the main goal in mind when dealing with Android.

Regarding the Parcelable itself, consider that it's merely adds additional methods for model object in order to make Android OS be able to serialize/deserialize data between different system components. So as your tests in the domain level doesn't run by Android OS, they should not touch this methods and it would not affect your tests.

Consider, several other APIs in Android that are not available in unit test, like Uri, DateUtils, SparseArray and more...
That's where I think that Roboelectriccan come handy, with mocking these Android primitives.

Having said all that... with Clear Architecture, your Domain level should be separated from Presentation level, so basically you would have model objects in both layer (that can share interface) and both of them can use AutoValue, but, only in Presentation level you can implement the Parcelable interface (which are the ones that needs it, as in this level you'll interact with the System and use Parcel). No Android dependencies in the Domain level are not the only consideration for this separation, bear in mind, that Presentation level might add information that is not relevant to Domain level.

You can't add two support libraries as they overlap each other. Just use one: support-v4.