[CRITICAL] Can't Publish or create private codes on 1.0 to UEFN converted maps

General Issues and Bug Reporting
, ,
1

Reference ID

b3f8b025-435e-90df-4750-25bb244f39c4

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Summary

After transferring maps built in Creative 1.0 to UEFN and updating them in UEFN we can no longer publish them or create private codes. Error Message: [DEP] valkyrie-source-content-live.s3.amazonaws.com returned unparsable JSON response SentryEventId=d7b709c2b6a94f5ca7ee6020c56dae85

Steps to Reproduce

Create a map in Creative 1.0 (this may need to have been an old island, idk, ours were fairly old). Convert it to UEFN. Try to create a private code / publish.

I also put these maps on a TEAM after transferring and enabled revision control.

Expected Result

Able to create private codes and publish without an error code.

Observed Result

An error code and the inability to publish these maps or create private codes.

Platform(s)

windows

Island Code

5203-1483-3698

2

UCB-1075 incident has been created. Status is ‘Awaiting Validation’.

3

Hey Puzzler, I think a few other Epic folks reached out but I’m commenting for anyone else.

If you’re trying to convert from FNC to UEFN please make sure that all accolade devices in your map do not have any newlines (i.e. all text on one line) in the Device Name or Description for the time being. We’re working on a fix but in the meantime this is the easiest workaround we’ve found.

Sorry for the hassle.

4

Also @PUZZLER if you could confirm that workaround helps that would be great :smile:

5

Hello HalcyonKnight69,
The error also occurs with maps that were created only in UEFN. Is there already any suggestion for a solution to this?

6

@HalcyonKnight69 Oh, cool… Thanks for the tip!
When I deleted the 2nd line I was able to upload a private version.
I hope this fixes it for me and the error doesn’t appear again.

7

For anyone looking for a fix I can confirm removing new lines/emojis or anything weird from your Accolades Devices does fix it. Thanks for the help!

1 Like