Fixed
Status Update
No update yet.
Comments
yb...@google.com
yb...@google.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.
Description
Version used: `1.0.0-alpha3`, / `1.0.0-alpha8`
Devices/Android versions reproduced on: I can verify the problem in a Unit test
Description:
When we use a Flowable to get an update notification after inserting a new data-base row, works fine.
But when the insertion is done inside another explicit transaction, the Flowable does not get a notification.
- Sample project to trigger the issue.
To illustrate the issue, I've forked the BasicRxJavaSample from android-architecture-components and added 2 test-methods to UserDaoTest.java:
see failing test: testFlowableInTransaction
for more details and formatted code see: