Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.1
Issue ID
1213506
Regression
No
ApiUpdater may leave orphan usings when only type qualified references were present in the source
In some scenarios after ApiUpdater runs old, non existing namespaces may be left in using clauses.
This may happen if Unity changes a type to a namespace that already exists and is already imported in the script.
For instance, consider the following:
// In UnityEngine.dll
namespace UnityEngine.Foo
{
class Bar {}
class Baz {} // Originally in UnityEngine.Other
}
// in user code
using UnityEngine.Foo;
using UnityEngine.Other;
class C : UnityEngine.Other.Baz
{
}
When ApiUpdater finishes updating user code it will looks something like:
// in user code
using UnityEngine.Foo;
using UnityEngine.Other; // Should have been removed
class C : Baz
{
}
Comments (63)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
sovojacket
Apr 14, 2021 16:02
Thanks