I also have this issue. started after the update. i need to urgently update my map 
Hello,
I’m currently having the same problem.
I’m having this same problem since after the update
Thank you, we’re investigating.
hi @Flak, i have same problem, can you help me?
Yup getting the same issue, started a few hours ago. When I rollback to a version that was working this morning and last night it still breaks but when I rollback to before the last update it works so looks like whatever that thing was that ran when we opened our maps after the update and changed almost all our assets is causing the issue and they changed how it was handled server side a few hours ago. This is just my speculation after wrestling with it for a few hours
This issue seems like it will take some time to resolve, so for now, I restored a snapshot from before version 35.00, and the problem no longer occurs. Since then, I’ve been carefully adding and removing assets one by one, making sure that live edit remains functional as I continue working.
Hi @Flak . I have the same problem, I need to update my map. Do you have news?
I found a way to avoid it After encountering this error.
In my case, there was an asset I had deleted from the map before the error appeared, but a reference to that deleted asset still remained in the settings of another asset.
Once I removed that reference manually, the error no longer appeared and I was able to start live edit successfully.
(For example, a deleted asset was still referenced in the settings of a Verse device.)
So, it might be a good idea to carefully check if there are any assets that still contain references to deleted ones.
I hope this information is helpful.
I managed to get past this error when I experienced it post upgrading to v35.0.0
In my situation, I noticed that a vfx spawner device in my level got modified. I was using a custom niagara effect on this device. When I deleted the niagara effect and remade it, everything cooked again perfectly fine.
Something happened with this update that caused peoples editors to corrupt assets.
Removing all the Verse devices on my map solved it. Now it’s just a matter of finding which device was the cause and why.
Hi everyone,
Just wanted to share a quick update in case it helps someone else running into a similar issue.
Here’s how I managed to fix it:
- First, I made sure to check in changes so I could revert back.
- Then, I removed all Verse devices and started the session.
- After that, I reverted all files to bring the Verse devices back and pushed the changes.
- At this point, the errors related to the Verse devices were finally clear and easy to resolve — I just clicked on the errors and removed the missing references.
Everything works fine now. Hope this helps someone dealing with a similar issue!
1 Like
I still have the problem now (it’s been 1 week)
this one didnt help me. still getting error
@Flak Any update on this?
Same problem here
So I’ve narrowed it down to if I have any verse in my map I cannot connect to a session and I can’t fix it. Really need to be working on the map I wanted to submit it for TMNT builder challenge this month
Started again today. This time I just deleted each device, pushed, ctrl+z until everything was back where I started and it works again …
For me, this issue was resolved by removing my Verse devices.
Did anyone find a fix for this yet? I’m still getting this error message on any of my maps created before V35.
@Flak is there any plans to push a fix for this next week to release alongside the main Fortnite update?
2 Likes