Summary
[43.00] Publish blocked by “Ambiguous identifier” in the previously-published version (sys/published), the new candidate is clean
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Publishing
Steps to Reproduce
- Live island 3007-3425-6195, published before 43.00. Its live version has a field “Notices” in money_rush_device.verse and an asset folder “MoneyRush/Notices”.
- In 43.00, rename the field to “NoticesJoueurs” and the folder to “MR_Annonces”. The project compiles with no errors.
- Upload a new version (candidate 9972-1862-0009?v=1) and try to publish it in the Creator Portal.
Expected Result
The new candidate passes Verse validation and can be published.
Observed Result
Publishing fails 4 times (lines 982, 985, 1350, 1352) with:
Ambiguous identifier; could be (/goratek@fortnite.com/MapTROT/money_rush_device:)Notices or (/goratek@fortnite.com/MapTROT/MoneyRush:)Notices
in file: C:/build/FortniteGame/Plugins/GameFeatures/c316d81f-858b-4e6c-9f2b-6f80b23c3362/sys/published/Content/money_rush_device.verse
The candidate no longer contains this identifier or this folder. The reported lines match the currently LIVE version, not the candidate.
Platform(s)
UEFN 43.00 (Windows), Creator Portal publishing
Island Code
3007-3425-6195
Additional Notes
The backwards-compatibility (persistence) check seems to recompile the previously-published version with the 43.00 compiler, which now treats “Notices” as ambiguous. A published version can’t be edited, so creators can’t fix this themselves. The UEFN upload log also says “Verse backwards compatibility checking was disabled”, so the error only shows up on Epic’s side.
This issue is not in the v43.00 Known Issues list. The same issue happened in 38.00 and was fixed server-side (thread: “[CRITICAL] After 38.00, it is not possible to launch the project”).
Module: c316d81f-858b-4e6c-9f2b-6f80b23c3362. We don’t want to create a new island, to keep players and their saved data.