Fixed
Status Update
No update yet.
Comments
ga...@gmail.com
I should probably elaborate on that a bit more here :P. The ideal case would be that data classes written in other modules work the same when consumed. A standard data class (no secondary constructors, `val` properties) works fine when in the same module. The errors produced are also pretty confusing. They'll usually give what they read from the bytecode (constructor params called "var0" or the like) and reports missing setters for fields without names of said fields.
yb...@google.com
yb...@google.com
I can confirm the bug and the workaround. The same problem arises when you use a data-class from a library with @Embedded
yb...@google.com
given that log, looks like kotlin again not generating proper parameter names for methods.
Description
Version used: 1.0.0-alpha9
The errorHandler field of SupportSQLiteOpenHelper.Configuration[0] uses android.database.DatabaseErrorHandler[1]. The problem is that the onCorrupted method of DatabaseErrorHandler has android.database.SQLiteDatabase as parameter, which custom implementations won't have an instance of because they write their own implementation of android.arch.persistence.db.SupportSQLiteDatabase[2]. My proposal would be to add a SupportDatabaseErrorHandler which uses SupportSQLiteDatabase instead of the platform one.
[0]:
[1]:
[2]: