Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.11
Issue ID
VS-78
Regression
No
Intellisense is not detecting Unity-specific suggestions when a script is part of an Assembly
How to reproduce:
1. Open the user-attached “TestAssemblySwitch.zip” Project
2. Open the “PlayerController.cs” Script found in the Assets/Scripts/InputSystem folder
3. Attempt to write awake/start/update functions in the Script
4. Wait for the Intellisense suggestions to appear
Expected result: Intellisense Unity suggestions window appears
Actual result: Intellisense suggestions appear but without Unity-specific suggestions
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a7
Reproduced on: macOS Ventura 13.5 (Intel), Windows 11 (User reported)
Not reproduced on: No other environment tested
Notes:
- Issue might be highly inconsistent to reproduce, first-time testing was not reproducible
- Couldn’t reproduce on a new project
- Reproducible with Visual Studio 2022
- Not reproducible with Visual Studio Code
- Couldn’t find under what condition the issue starts reproducing
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
On Mac please note that VS for Mac is not supported anymore (VSCode is the new preferred Editor on this platform). On Windows we were unable to reproduce this issue. Please Make sure to use the latest VS Editor package and Visual Studio 2022.