Fixed
Status Update
No update yet.
Comments
ch...@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
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
ya...@google.com
ch...@gmail.com
given that log, looks like kotlin again not generating proper parameter names for methods.
Description
Version used:alpha1
Devices/Android versions reproduced on:Samsung S7
Entity with a column having byte[] as primary data type has issues reading it
android.database.sqlite.SQLiteException: unknown error (code 0): Unable to convert BLOB to long
at android.database.CursorWindow.nativeGetLong(Native Method)
at android.database.CursorWindow.getLong(CursorWindow.java:524)
at android.database.CursorWindow.getShort(CursorWindow.java:575)
at android.database.AbstractWindowedCursor.getShort(AbstractWindowedCursor.java:63)
Sample query: SELECT test from test_device WHERE serial_number = ?
here is test is of type byte[]