Packaging Fails with 'ICUInternationalization data file' Error ONLY in Original project Directory (UE5)

Development Platform & Builds
, , , , , , ,
1

Hi everyone. I’m running into a packaging issue that has me a bit confused.

The project compiles and cooks content without any issues. Everything proceeds normally up until the very end of the packaging process, where it suddenly fails with the following error:

LogWindows: Error: begin: stack for UAT
LogWindows: Error: === Critical error: ===
LogWindows: Error:
LogWindows: Error: Assertion failed: U_SUCCESS(ICUStatus) [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\Internationalization\ICUInternationalization.cpp] [Line: 162]
LogWindows: Error: Failed to open ICUInternationalization data file, missing or corrupt?
LogWindows: Error:
LogWindows: Error:
LogWindows: Error:
LogWindows: Error: Crash in runnable thread Foreground Worker #1
LogWindows: Error: end: stack for UAT
LogWindows: FPlatformMisc::RequestExit(1, FRunnableThreadWin::GuardedRun.ExceptionHandler)
LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, FRunnableThreadWin::GuardedRun.ExceptionHandler)

I already attempted a full cleanup by removing all generated files and keeping only the Source, Content, and Config folders, along with the .sln and .uproject files. Unfortunately, the packaging error persisted.

Interestingly, if I copy those same folders and files into a completely new directory (different from the original project path), the packaging process succeeds without errors.

I’m trying to understand what could cause the project to fail only when packaged from its original directory. Any insights or suggestions would be greatly appreciated.

2

Hello there @SkyTree_0!

No worries, I think it’s a simple matter. The original location on your log has a quite lenghty string, which usually results in the compiler returning an error.

Meaning, this should not be related to project corruption, it’s just the OS not being able to handle the extended directory location. Keep your folder path’s short, and this issue should not reappear.

1 Like
3

Interestingly enough the copy that packages successfully has a longer path length than the original one. I named the copy folder “ProjectName_Copy”.

Basically, if the original was: V:\Projects\UnrealEngine\ProjectName\

then the copy is: V:\Projects\UnrealEngine\ProjectName_Copy\