Verified
Status Update
No update yet.
Comments
yb...@google.com
Trying to find a temporary work-a-round I found that `MediatorLiveData` also doesn't work, as it internally also calls observeForever/removeObserver.
The only work-a-round I found is very hacky and only works on this specific scenario is to `post` to a Handler to `removeObserver` later.
It works only on this case because the background processing only happens when the network call is successful (a.k.a. the LiveData won't values anymore).
The only work-a-round I found is very hacky and only works on this specific scenario is to `post` to a Handler to `removeObserver` later.
It works only on this case because the background processing only happens when the network call is successful (a.k.a. the LiveData won't values anymore).
fa...@gmail.com
Thank you for a report!
Yeah, your work around is fine for now. This is going to be fixed in alpha-9.
Yeah, your work around is fine for now. This is going to be fixed in alpha-9.
yb...@google.com
Also, you can try go down to alpha-5, it may be fine there.
[Deleted User] <[Deleted User]>
hi "se...@google.com"
it seems that rolling back to alpha-5 solved it, and I'll be looking forward to alpha-9.
Is this bug brand new or something the team was already aware of?
thanks.
it seems that rolling back to alpha-5 solved it, and I'll be looking forward to alpha-9.
Is this bug brand new or something the team was already aware of?
thanks.
yb...@google.com
No, we weren't aware of that. But we added tests for underlying issue.
[Deleted User] <[Deleted User]>
Great. Super happy to help!
[Deleted User] <[Deleted User]>
alpha9 was pushed. It is fixed there.
yb...@google.com
thanks for the sample app! I'll debug and see why the error does not show properly.
about the other bug, it is actually a jdk bug :/
https://bugs.openjdk.java.net/browse/JDK-8007720
about the other bug, it is actually a jdk bug :/
yb...@google.com
so the element about which we report the error seems fine.
I'll try to convert it to java and see if it will have the same problem.
I'll try to convert it to java and see if it will have the same problem.
yb...@google.com
same in java. Looks like annotation processor cannot report an error on its dependency class :/. We need to figure out a way to either resolve it or at least discover that it is coming from a dependency and report manually.
[Deleted User] <[Deleted User]>
Any updates on this?
It's very, very difficult and time-consuming to debug Room errors in big projects.
It's very, very difficult and time-consuming to debug Room errors in big projects.
yb...@google.com
sorry we don't have anything here yet :/. it will be post-IO :(.
yb...@google.com
da...@google.com
da...@google.com
This fix will be available in 2.0.0 beta 2.
cc...@google.com
Fix went in early enough to get into 2.0.0-beta01, so marking released
da...@google.com
The file links in #16 have restricted access. Are you still seeing the issue and are trying to show us through those screenshots?
Description
Version used: 1.1.0-alpha5
Devices/Android versions reproduced on: Compile-time error
Android Studio & tools: Studio 3.0.1, gradle-build 3.0.1
When getting an error from the Room annotation processor in a Java environment, the Gradle error doesn't include any mention on the class nor the field. I.e. "cannot find getter for field". This means that it's incredibly difficult to debug this kind of issues.
This is also happening when using --info, --debug or --stacktrace as the gradle task parameter.