UEFN Moderation Warning opens an Empty Blank Tab instead of a list of Moderated Assets

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Summary

I received a “Project Moderation Warning”, but it does not tell me which asset/s are problematic.

Steps to Reproduce

Open project, wait for moderation warning pop up, click “Open Creator Portal”

Expected Result

After clicking “Open Creator Portal” I should see the name of the problematic asset like usual

Observed Result

After clicking “Open Creator Portal” I see nothing, it only opens a blank New Tab in my browser.

Platform(s)

Windows 11 PC

Island Code

4079-8665-8628

Additional Notes

Issue persists after restarting PC. Issue persists after updating PC. Issue persists on other Windows computers.
I imported a few hundred textures, I manually sifted through to try and find problematic ones but maybe I missed something?

I have same problem

2 Likes

Same problem here, After the new update, all of a sudden something is violating guidelines. Finding out which asset violates the guidelines? Good luck…

2 Likes

The status of FORT-737430 incident has been moved from ‘Ready for QA’ to ‘Closed’. Resolution Reason: ‘Cannot Reproduce’

3 Likes

I also cant start up a UEFN session at all since the 29.30, Possibly also caused by the moderation popup launching each time i try to start a session. When i dismiss the message, my screen gets stuck at “Loading into session”. I literally cannot do anything at the moment. resolving this issue might help.
image

3 Likes

Same here, right after it showed in Check-in Changes this files…

2 Likes

Same issue here, the moderation notice orginally opened in my browser, now it just opens an empty tab, and I can’t even launch session anymore because of it.

3 Likes

Have you found a work around? I am having the same issue

My issue has been fixed, I can now relaunch my session and i have no more warnings.

Since the 29.30 added new functionality to reference UMG widgets in verse, an existing widget i had made had an Ambiguous name to a class or instance in verse. Removing / Renaming this widget solved the problem for me.

2 Likes

Issue persists for me :smiling_face_with_tear:

Hey folks - we’re looking into this issue. In the meantime, we’ve had some individuals get unblocked by changing something in their projects ever so slightly, and recooking. Let us know if this works for you.

3 Likes

We are having the same issue. We notice that in the two projects or ours that have the issue, there is no assets.digest file. We suspect it’s not a coincidence that we are facing this issue only in our projects that have the missing file. But we don’t understand why it was not generated.

What did you mean by “recooking”? We tried to recompile Verse, but that didn’t change anything.

I learned that the missing assets digest file is not related. :sweat_smile:

It’s an older project so I had to enable the feature manually as described in Exposing Assets in UEFN to Verse . After enabling the assets file is generated correctly.

I was hoping that this would resolve the empty tab issue that should display the flagged assets. But it’s not the case. So we’re still blocked and made several “slight” changes that didn’t trigger a solution like an earlier reply on this thread suggested

Just got my issue resolved, changing a function name… After I got a message with filename and line where the problem was.

where did you get the message

yeah same

1 Like

I’m having this same exact issue. It’s giving me a moderation warning and when I click on it, it brings me to a blank tab. I don’t know what the problem is and how to fix it. I can’t even launch a session or push changes.

1 Like

Hi, I’m running into this issue almost exactly as OP (except im on Windows 10) and I have tried reverting back to a version from yesterday which was not having any issues. I have tried deleting assets and tried just about everything. It won’t let us push changes or launch sessions. Send help…

1 Like

Any update Amanda?

The team is still digging into this today! Will let you know if we have an update!

1 Like