System.NullReferenceException for script that apperantly dosent exist

Unity Engine
,
1

im using unity 2022.3.2f1 and i am getting a error when loading a project folder that says the following:
System.NullReferenceException: Object reference not set to an instance of an object.
at ApiUpdater.MovedFromOptimizer.Program.CollectMovedFromTypeNamesFromAssembly(String assemblyPath, StreamWriter outputFile, IAPIUpdaterListener logger) in /Users/bokken/build/output/unity/unity/Editor/Tools/ScriptUpdater/ApiUpdater.MovedFromExtractor/Program.cs:line 85
at ApiUpdater.MovedFromOptimizer.Program.RealMain(String[ ] args) in /Users/bokken/build/output/unity/unity/Editor/Tools/ScriptUpdater/ApiUpdater.MovedFromExtractor/Program.cs:line 41
at ApiUpdater.MovedFromOptimizer.Program.Main(String[ ] args) in /Users/bokken/build/output/unity/unity/Editor/Tools/ScriptUpdater/ApiUpdater.MovedFromExtractor/Program.cs:line 17
ive searched my project folder for this but i cant find Program.cs and i tried deleting the libary folder to no avail. help me :frowning:

2

ok, i know know that bokken is the build bot, but how do i get the error message to go away

3

just delete the plugins folder and that would regenerate and make a new one and the error code should be gone.

4

I deleted it but now i have 513 errors :sob:

5

Well I would say “restore from a backup” but I’m going to guess that you might not have one. In the future remember that actually deleting the folder isn’t necessary. If you renamed it the folder would appear to Unity to have been removed.

That way you could rename it back when it doesn’t work.

6

This error is from Unity’s internal API Updater, not your project — that Program.cs file doesn’t exist in your folder. It usually happens when there’s a missing or broken script/component in your project or cached metadata.

What to try:

  1. Delete the Library, Temp, and obj folders, then reopen the project.
  2. Look for Missing Scripts on GameObjects and remove them.
  3. Go to Assets ==> Reimport All to rebuild metadata.
  4. If it persists, check the Editor.log to see which assembly triggers the updater.

Usually, cleaning the project folders and fixing missing scripts resolves this.