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
{
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Audio sound is lower in the Player compared to the native music player
- Feet slide and misalign when playing retargeted animations
- IndexOutOfRangeException is thrown in NativePassCompiler when a graphics buffer is used in more than 5 render passes
- "Undo Stack Overflow" error is thrown, and Undo History is deleted when multiselected GameObjects are reparented to their GrandParents
- SearchColumn of type "ObjectReference" does not get refreshed for the custom SearchProvider when lighting generation finishes
Add comment