Search Issue Tracker
Fixed
Fixed in 2022.2.3f1, 2023.1.0a26
Votes
0
Found in
2022.2.2f1
2023.1.0a24
Issue ID
UUM-21715
Regression
Yes
Additional files are not always considered as input into the compilation pipeline when passed as input to Roslyn source generators
Reproduction steps:
1. Open the “SourceGeneratorTest_2022“ project
2. Open the “Assets/Code/Gameplay/LocalisationKeys.LocalisationKeysSourceGenerator” file
3. Modify the “ABOUT_CREW” key (e.g. to “BOUT_CREW”) and save
4. Return to the Editor and observe the Console
Expected result: “Assets/Code/Gameplay/MainCharacter.cs(11,36): error CS0117: 'LocalisationKeys' does not contain a definition for 'ABOUT_CREW'“ error
Actual result: Missing an error about the “ABOUT_CREV” key referenced in the “CharacterController” script being undefined
Reproduced in: 2022.2.0b1, 2022.2.2f1, 2023.1.0a1, 2023.1.0a24
Not reproduced in: 2021.3.16f1, 2022.2.0a19
Could not test in: 2020.3.43f1 (“'LocalisationKeyList' could not be found” error)
Reproduced using: macOS 13.0.1 (Intel)
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2023.1.0a26):
Fixed in 2023.1.0a26
Resolution Note (fix version 2022.2.3f1):
Fixed in 2022.2.3f1