Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
1
Found in
2020.3.43f1
Issue ID
UUM-22930
Regression
No
"Timeout while updating assemblies" error when updating DLLs
How to reproduce:
1. Open the attached project “DLLerror.zip“
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Update DLLs (MISSIM > Build All)
Expected result: DLLs are updated
Actual result: “Timeout while updating assemblies:Assets/Battlehub/RTSL_Data/RTSLTypeModel.dll (Output: /var/folders/wl/vrvcpxqs0r93nknq1ths3d8r0000gp/T/tmp1495ea10.tmp)“ Error in the Console
Reproducible with: 2020.3.43f1
Can’t test with: 2021.3.16f1 (Errors in the Console), 2022.2.2f1, 2023.1.0a24 (errors “Failed to find entry-points: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly”)
Reproduced on: 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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2020.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.