Fixed
Status Update
No update yet.
Comments
il...@google.com
that is weird. might be a studio issue, can you share the output of gradle? (the output from command line)
[Deleted User] <[Deleted User]>
Here it is, with --info.
Since the module is a mixed Java/Kotlin one, I have tried with both annotationProcessor and kapt.
The result is the same, no indication about the failure.
Since the module is a mixed Java/Kotlin one, I have tried with both annotationProcessor and kapt.
The result is the same, no indication about the failure.
il...@google.com
that is so weird, we always report that error w/ a reference to the field:
context.checker.check(success, field.element, CANNOT_FIND_GETTER_FOR_FIELD)
can you share your build.gradle file? Which version of kotlin are you using?
Also, make sure you have kotlin-kapt plugin applied.
Also, I realized that you've put version 1.1.0-alpha5 which does not exist. Did you mean 1.1.0-alpha1 or 1.0.0-alpha5 ?
context.checker.check(success, field.element, CANNOT_FIND_GETTER_FOR_FIELD)
can you share your build.gradle file? Which version of kotlin are you using?
Also, make sure you have kotlin-kapt plugin applied.
Also, I realized that you've put version 1.1.0-alpha5 which does not exist. Did you mean 1.1.0-alpha1 or 1.0.0-alpha5 ?
il...@google.com
Apologies, I meant to write 1.1.0-alpha1.
Worth mentioning that the @Database class and the @Entity are in two different library modules, one directly depending on the other.
Both modules are using Kotlin version 1.2.21, kotlin-apt and `kapt "android.arch.persistence.room:compiler:1.1.0-alpha1"`
and `implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.2.21"`.
Worth mentioning that the @Database class and the @Entity are in two different library modules, one directly depending on the other.
Both modules are using Kotlin version 1.2.21, kotlin-apt and `kapt "android.arch.persistence.room:compiler:1.1.0-alpha1"`
and `implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.2.21"`.
[Deleted User] <[Deleted User]>
so you are probably hitting
But in terms of why the error is not populating, i'm still baffled :/. The sample in
Is it possible for you to create a sample project that reproduces the error?
But in terms of why the error is not populating, i'm still baffled :/. The sample in
Is it possible for you to create a sample project that reproduces the error?
lo...@gmail.com
Sure thing. I've created a super simple test project where the error output is the same.
Again, latest Android Studio latest stable release (3.0.1) on Mac OSX 10.13.3, embedded JDK.
Again, latest Android Studio latest stable release (3.0.1) on Mac OSX 10.13.3, embedded JDK.
mu...@gmail.com
Not sure these two bugs are related (I've added a comment here, despite it being closed: https://issuetracker.google.com/issues/69562125 ), but in the same test project it's also very easy to reproduce another issue.
By just adding the `@IntRange` annotation to the `id` field in `TestEntity` (and uncommenting the getter), the compilation breaks again, this time kapt fails with this message: "Error:error: Entities and Pojos must have a usable public constructor. You can have an empty constructor or a constructor whose parameters match the fields (by name and type)."
Annotating parameters in the constructor used by Room breaks it.
By just adding the `@IntRange` annotation to the `id` field in `TestEntity` (and uncommenting the getter), the compilation breaks again, this time kapt fails with this message: "Error:error: Entities and Pojos must have a usable public constructor. You can have an empty constructor or a constructor whose parameters match the fields (by name and type)."
Annotating parameters in the constructor used by Room breaks it.
[Deleted User] <[Deleted User]>
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 :/
[Deleted User] <[Deleted User]>
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.
il...@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.
h....@gmail.com
sorry we don't have anything here yet :/. it will be post-IO :(.
Description
DETAILS:-
The destination home is an activity with a NavHostFragment (FirstFragment.kt) which initially navigates to the second destination (SecondActivity.kt), then immediately comes back to the FirstFragment, and then navigates to third destination (FirstPopupFragment.kt). (Navigation can be observed in the attached screen-record).
LOG:-
2018-05-27 20:39:52.794 3289-3289/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.cyrilnoah.navigationegapp, PID: 3289
java.lang.IllegalArgumentException: navigation destination com.example.cyrilnoah.navigationegapp:id/action_first_to_first_popup is unknown to this NavController
at androidx.navigation.NavController.navigate(NavController.java:605)
at androidx.navigation.NavController.navigate(NavController.java:565)
at androidx.navigation.NavController.navigate(NavController.java:553)
at com.example.cyrilnoah.navigationegapp.FirstFragment$onViewCreated$1.onClick(FirstFragment.kt:40)
at android.view.View.performClick(View.java:6579)
at android.view.View.performClickInternal(View.java:6556)
at android.view.View.access$3100(View.java:777)
at android.view.View$PerformClick.run(View.java:25660)
at android.os.Handler.handleCallback(Handler.java:819)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)
Component used:
"android.arch.navigation:navigation-fragment-ktx:$nav_version"
"android.arch.navigation:navigation-ui-ktx:$nav_version"
Version used:
nav_version = '1.0.0-alpha01'
Devices/Android versions reproduced on:
Tested on Pixel 2 XL (emulator), and Xiaomi Mi Max 2 (real device). Probably crashes on all, not so sure.
- Sample project to trigger the issue.
(Project attached below)
- A screenrecord or screenshots showing the issue (if UI related).
(Screen-record attached below)