I was able to duplicate my project and when I tried to publish it, it successfully validated the verse check so I think its something on Fortnites side that they need to fix. All we can do is just wait for them to fix it, unless someone else has figured out a way around it.
Opened a ticket describing my problem after fix in this thread:
Iâm having the same exact issue as you. the sys folder is empty, and my UI module is in conflict with scene graphâs one, even though I import it through
using { /myname@fortnite.com/ProjectName/UI/Materials }
This is happening on a published project with a community of players, and I now have to delay the update to I donât even know when.
Please @flak get someone to work on this, we canât wait until the next update (if it get fixed with the next update) to publish projects, itâs game breaking.
Iâm not sure about what you mean.

I also have a module pointer to declare all folders public, but that doesnât have to do with the issue Iâm facing.
The issue is about the import path inside using {}
I originally had problems with it and switched from using{ UI } to using { /myname@fortnite.com/ProjectName/UI }
And this shouldnât create issues.
My main confusion is you using the verse path itself as above ? Why do you need this when you have set the modules ?
Because otherwise it was causing conflicts with another UI module. Donât remember which one, maybe from Unrealengine/Temporary
I will try to change my module to a different name and see if it fixes it. Hopefully
Just delete the verse path and keep the modules ?
It would create conflict that way. I think the real big fix for the future is just donât name your folders generic names like UI, Materials etcâŚ
Hi (updated)
The problem is Scene Graph Edit, which is often automatically turned on
see
Scene Graph got enabled for your project unintentionally
Assertion failed: OwningNode
Classes\EdGraph\EdGraphPin.h
Someone with Scene graph experience, probably a new thread
not an ambiguous identifier
I never had scene graph turned on.
FORT-1006738 is âClosedâ as âFixedâ. The issue will be addressed in 38.11.

