Search Issue Tracker
Fixed in 2019.3.X
Votes
2
Found in
2019.1.0b7
2019.1.0b9
Issue ID
1140618
Regression
Yes
An forced package upgrade causes Library Cache compile errors in TextMeshPro package after project upgrade
This simple example project is made using 2018.3. It uses TMP version 1.3.0.
After upgrading to 19.1.0b9, i get a lot of compile errors in Library\PackageCache - so unrelated to the Project's scripts.
Repro:
- download this example project from here: https://oc.unity3d.com/index.php/s/ENtPN4z0qkTCAm2
- Open it with 19.1.0b9
- automatic package upgrade should trigger, though on some PCs, I had to go to Help->reset packages to default"
- Notice that, after you clear the console tere will be compile errors in
Library\PackageCache\com.unity.textmeshpro@2.0.0\Scripts\Runtime\TMP_InputField.cs(944,33): error CS0115: 'TMP_InputField.OnValidate()': no suitable method found to override
- If you exit Unity and delete that folder again, these errors will go away
Reproducible on 19.1.0b7, b8 and b9
Not reproducible on 18.3.8f1, 19.1.0b3 an 19.1.0b6 or in 2019.2.0a10
Note: this seems to have been fixed or the behaviour has changed in some way that's not reproducible anymore in 2019.1.0b10
Comments (2)
-
Sukender
May 16, 2019 09:53
Similar issue with TextMeshPro 2.0.0 and 2.0.1.
Also had a 3rd-Party plugin with similar error. It contains a few "protected override void OnValidate()" in UIBehaviour derivates. I first removed "override" and made Unity compile. Then it suddenly complained about "override" being missing! I reverted my changes and compilation was finally okay. I reproduce this error every time I upgrade Unity. Clearing Library/ScriptAssemblies doesn't help.
-
Toylips
Apr 16, 2019 13:32
I have the same in 2019.1.0f2
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
- ArgumentOutOfRangeException is thrown when an empty DropdownField is clicked at runtime
- [tvOS] "EXC_BAD_ACCESS" error is thrown when Painter2D.ClosePath is called
- Bad Naming Convention in Shortcuts Window for Sprite Shape Editing
- Bad Naming Convention in Shortcuts Window for Shader Graph
- Bad Naming Convention in Shortcuts Window for Particle System
Resolution Note (fix version 2019.3):
This behavior has historically been like that in the Editor (possibility of script compilation starting before importing all script assets), and has become more visible with the increasing use of packages.
It has been fixed by the Assets Pipeline V2 that will be released in 2019.3.