I’ve run into a bug that starts with looking up any definition (F12) for the second time, with files that are in a Package (any package, Localization shown here for example). The first time it opens the file everything is fine, as shown in the first image. Every time after that, when opening the same file, it comes up looking like the second image. I’m using Unity 2022.3.16(/28) and VS Community 2022, v17.7.6 and then v17.12.3. Happens in local projects including a brand new one, as well as projects cloned from GitHub. Windows 10 Pro, 22H2. VS 2022 is correctly set as the External Script Editor in Preferences.
This only seems to happen with scripts that are in packages, as opposed to any of the built-in engine stuff.
Closing VS resets this.
It seems to be ok as long as the Tab with the external script is still open (third image). If it’s closed or swapped out for any other file, next time it opens the problem happens.
Has anyone else run into this? Any solution if so?