Search Issue Tracker
Fixed
Fixed in 2022.3.29f1, 6000.0.2f1
Votes
0
Found in
2022.2.16f1
2022.3.0f1
2023.1.0b13
2023.2.0a11
2023.3.0a3
6000.0.0b11
Issue ID
UUM-33752
Regression
No
Redundant precompiled assembly changes when Editor prompts for updates
How to reproduce:
1. Open the user-attached “My Project” project
2. When prompted to update precompiled assemblies, select “yes”
3. Extract “DLL_Check”
4. Locate the 4 updated .dll files in the project and copy them to the “DLL_Check” folder
5. Add the “Upgraded_” prefix to the pasted files
6. Run “file_checker.bat”
7. Open “differences.txt” (see the attached “how_to” image)
Expected result: all 4 precompiled assembly files are different
Actual result: only 1 precompiled assembly file “Atesh.MagicAutoLinker.dll” is different
Reproduced with: 2022.2.16f1, 2023.1.0b13, 2023.2.0a11
Could not test with: 2020.3.47f1, 2021.3.23f1 (DLLs have reference errors)
Reproduced on: Windows 11
Notes:
1. Project has been stripped and downgraded to Unity Editor version 2019.4.34f1 in order to confirm if the issue is reproducible on versions before 2022.2
2. For Unity Editor version 2022.2.16f1 and above, the user-attached project was used
3. For Windows I created a simple batch script that uses “fc.exe” to compare files: [https://www.computerhope.com/fchlp.htm]
4. For reproduced versions, outputs are provided in attachments
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 6000.0.2f1):
Closing the tickets since the PR with the fix already landed on a previous version
Resolution Note (fix version 2022.3.29f1):
This bug describe multiple issues:
1. Unexpected updates to `System.Runtime.CompilerServices.IsExternalInit`
2. Dangling (non Unity) assembly references being removed
3. Unexpected recompilation compilation (most likely a side effect of point 2)
The first issue has been fixed around May/2023.
The second one has just been fixed and should be included in the next builds.
The third one is a side effect of the first 2 and should not be a problem anymore.
The provided repro project generates other, unrelated errors (at least in 2023.3) but we verify that the fixes are correct by inspecting the Editor logs and ensuring that updates *1* and *2* are not applied.