IssueTracker

Forgot to add the second screenshot. Here it is

Hi! I don't seem to be able to reproduce this behavior. As far as the resolution goes, these are treated exactly the same under the hood so I'm not sure how there would be a discrepancy.

I did notice that in your example, you are missing a semicolon after "age" in the PersonView, and when I left that out, I got the same issue with things not resolving, but once I put the semicolon then everything worked as expected. Just want to verify that that's not the cause.

The missing semicolon is a typo from my part and shouldn't change the behaviour in the issue. In my own code, I also have a semicolon. Unfortunately I don't seem to be able to edit the issue description.

Maybe the issue only arises in certain situations? I gave a simplified version of the problem with simple objects, but in my project I have database view on joins. I made sure that the simplified version of the issue also arises syntax errors in my own project though. Maybe something else clashes with it?

At the moment of writing, there are 2 other persons who also seem to have the issue (looking at the "I am impacted" vote count), so it seems that I'm not the only one with the issue, but weird that you can't seem to reproduce with my example.

Let me try to reproduce the issue in a clean project. Give me day or two for that.

Thank you! That will help immensely.

I created a fresh project, and I still got the error. I did find something interesting though, and that is that the issue occurs (for me at least) when I add the @Dao annotation. Before that, I do not get the error and the columns and view in "SELECT name FROM PersonView" are actually linking with the field and class respectively.

What I mean with that, is when you click with your mouse wheel (or ctrl + b) on name, it actually goes to the name field in PersonView. And when you click on PersonView it also actually goes to that class. But after I add @Dao, I get the error as described above (name and PersonView become red and get "Cannot resolve symbol ...").

So it seems as if @Dao is breaking the connection / link to the class? How far did you setup a project to reproduce the issue? Are you using the same versions as described in the issue? In my clean project, I used higher versions:

AGP: 8.7.3
Gradle: 8.9

The rest is the same:
Java: 18
OS: Windows 11
Studio Build: Ladybug | 2024.2.1 Patch 3

So even in higher versions of AGP and Gradle, the issue still persists. I used higher versions in my clean project to eliminate the possibility that the issue might have been fixed in a higher version.

I can share the setup project on GitHub if you'd like to. But don't know whether it will help since the issue seems to relate to the code editor, and not necessarily to the code itself. I didn't really create anything new except a database class, DAO class, an entity class and a view class.