[Major] Release verse validation servers always seem to use an older project state

[Velocity_Zero]

Summary

I updated my project after v40 and fixed all verse compilation issues. The game sessions runs fine and I can run memory calculation. However verse validation fails with the same error.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Check 6874-4972-3590 (failed private release code)

Expected Result

There were no verse persistence changes and all verse errors including the one that is reported as a failure have been fixed, checked in and all changes have been pushed.

Observed Result

Verse validation on the publishing services fails with the same error preventing me to publish a new release. Public release is already broken due to FORT-1076741.

vz_test_examples.verse(39,11, 39,13): Script error 3512: This invocation calls a function that has effects that are not allowed by its context: decides diverges

Platform(s)

PC

Island Code

2892-4984-5194

Upload an image

Additional Notes

The screenshot shows that I fixed the error that is raised by the publishing validation, which indicates that it’s likely using some past project state instead.

[Velocity_Zero]

I did fully uncommented the affected class, compiled, pushed and built a new release. The publishing validation still thinks it’s there and has pre v40 state, which makes it fail.

[Bug-Reporter]

FORT-1076934’s status has changed to ’Needs Peer Review’. A fix has been submitted, and is awaiting review by another team member.

[BangQZX007]

I also encountered a similar problem. I have already removed HunterItems from the code and repeatedly submitted multiple new versions, but the error keeps appearing. It seems that Verse’s verification is checking the content before version 40.00, and the newly submitted content of 40.00 was not successfully verified.

[Velocity_Zero]

Yes that’s exactly why it’s failing. The old game build is built with new tools but the new tools failing to provide backwards compatibility in our cases and thus we hit these validation errors.

Waiting for the fix to be rolled out.