In the latest update, we received an error stating that we have a name collision. After fixing the name collision in the main code, we still encounter the same issue, as the project fails validation at startup.
Most likely, the problem is that there is a cached project on the PC that shows this collision error: AppData\Local\UnrealEditorFortnite\Intermediate\sys...\%ProjectName%\...
Fix the error in the main project still prevents the project from running due to validation failure.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Stability
Steps to Reproduce
I don’t know, it happens 100% of the time on the project.
I have the same problem. There are no problems when opening the project, but as soon as it opens, an error appears (I will attach the logs below). I also noticed that this happens with my project in LEGO mode, but everything is fine with other created projects (even from other brands)
this also happen with verse files, I see the verse files in AppData\Local\UnrealEditorFortnite\Intermediate\sys...\%ProjectName%\...are not updated with changes made in the editor
I am still unable to publish and am getting this validation failed error message. I am also not sure if this is normal but my folder in ValkyriePublishedVerseFiles are empty
Interestingly, I got the same problem with one of my device instances, I recreated it in scene, published again, and problem persists… Maybe it is not connected to initial issue here, but maybe someone could help me here
Ive checked those and replaced all of those Ambiguous identifiers and am still getting the error in that script when I try and publish. Ive seen in another forum where people were saying the version that was published before the v38 update and had those Ambiguous identifiers couldnt be published since its not clearing the published fishing_manager code when checking the backwards compatibility or something like that
