<PACKAGE PROJECT> WORKED in 5.5.0, unknown error in 5.5.4 after 69 seconds

[2350lev]

same windows, same PC - It worked on 5.5.0, but it doesnt work on 5.5.4 ENGINE
+installed MORE of this - everything from here:

Setting Up Visual Studio Development Environment for C++ Projects in Unreal...

known problem from 5.5.0

AutomatedPerfTesting plugin does not build when building city-sample in ue5.5

From what I’ve seen the windows sdk configuration is probably fine. The memory is 32GB. The build was successful when I brought the files from github. Nothing else was done. If the build fails when you can start it in the editor, there may be some kind of bug. If the build fails even with ue5.4, this method cannot be used to resolve the issue. I heard that for 5.4 it’s a good idea to delete CitySampleCookedEditor.Target.cs.

saved files from 5.5.0 don’t work(I saved 3 working files), latest included from here are the same as from bellow ˘ and don’t work

example

$(EngineDir) = C:\Program Files\Epic\UE_5.5\Engine

copy file

$(EngineDir)\Plugins\Performance\AutomatedPerfTesting\Build\Scripts
├──AutomatedPerfTestConfig.cs
├──AutomatedPerfTestInsightsReport.cs
└──AutomatedPerfTestNode.cs

STRANGE ERRORS - SAME ERRORS last time that worked in 5.5.0 were conected to these 3 files ubove ^

UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2708,125): error CS1525: Invalid expression term ‘<’ (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2709,4): error CS1525: Invalid expression term ‘/’ (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2709,10): error CS1525: Invalid expression term ‘<’ (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2710,2): error CS1525: Invalid expression term ‘/’ (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2710,8): error CS1733: Expected expression (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): F:\Epic Games\UE_5.5\Engine\Plugins\Performance\AutomatedPerfTesting\Build\Scripts\AutomatedPerfTestNode.cs(2710,8): error CS1002: ; expected (F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj)
UATHelper: Packaging (Windows): Failed to build: F:\CPROGRAMS\Unreal Projects\CitySample\Build\Scripts\CitySample.Automation.csproj
UATHelper: Packaging (Windows): Build projects time: 69.27 s
UATHelper: Packaging (Windows): AutomationTool executed for 0h 1m 10s
UATHelper: Packaging (Windows): AutomationTool exiting with ExitCode=1 (Error_Unknown)
UATHelper: Packaging (Windows): BUILD FAILED
LogStreaming: Display: FlushAsyncLoading(376): 1 QueuedPackages, 0 AsyncPackages
PackagingResults: Error: Unknown Error
LogEOSSDK: LogEOS: Updating Product SDK Config, Time: 1006.949097
LogEOSSDK: LogEOS: SDK Config Product Update Request Completed - No Change
LogEOSSDK: LogEOS: ScheduleNextSDKConfigDataUpdate - Time: 1007.136536, Update Interval: 347.132782
LogText3D: Text3D Engine Subsystem is clearing unreferenced cached fonts and typefaces.

[brs-sebascova]

Hello there @2350lev!

Investigating around the community, I can confirm this is a known issue between the AutomatedPerfTesting plugin and UE 5.5.4.

Checking with my peers, the first step would be to ask if the plugin is needed 100% for your build, as disabling it during packaging would resolve the error. In case it is required, a possible workaround would be to backup its content, restore the version from 5.5.0, disabling file replace during buid, and try to pack the project again.