Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0b6
Issue ID
951261
Regression
Yes
Updating scripts results in an Internal error
Reproduction steps:
1. Open "networking_just_source.zip" project
2. On the "API Update Required" pop-up press "...Go Ahead!"
3. Update the scripts/assemblies Obsolete API's
Expected Result: The Obsolete scripts update
Actual Result: The Obsolete script update results in an Internal error/ API updating failed
Fixed in: 2018.1.0a1
Reproduced with: 2017.3.0b3, 2017.2.0f2, 2017.1.1p4, 5.6.3p4, 5.6.1p4, 5.6.1p2, 5.6.1p1, 5.6.1f1
Regression introduced in: 5.6.1f1
Did not reproduce on: 5.5.5f1
Note:
Internal error: Recursion detected while updating scripts (assembly index: 4 or assembly name: Assembly-CSharp.dll)
API updating failed.
Comments (15)
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
- “NullReferenceException” thrown when moving control points on a tree branch in Scene view
- [Linux] Player window unexpectedly resizes to monitor dimensions when calling "Screen.SetResolution" function with hardcoded resolution matching current display's width or height
- Color picker does not show the correct color when selecting color on the moving object
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
MrDude
Sep 09, 2018 10:34
Resolved my ass... 2018.2.6f1
twobob
Aug 02, 2018 18:39
This aint fixed
ModLunar
Jul 01, 2018 21:05
Yeah unforunately, it's still happening in 2018.2.0b10. Lol and I feel bad cause I know how annoying it can be to take the time to bugfix programming stuff..
LouisHong
May 31, 2018 01:14
Still happening in 2018.2
hjarenas
Feb 16, 2018 09:45
I am getting the same issue on a different project in version 2018.1.0b7. The original project was done in 2017.1.0f3