CRITIAL- Nintendo Switch Crashing (or not) in exact same island depending if its an editor_session/private_code/public_code

Hi @Jimbohalo10, thanks for your reply

I have the game updated on every device. I also have a microSD with 80GB available on the Switch. But just to be sure I uninstalled Fortnite and Installed it again on the Switch, but I still have the exact same issue.

I am able to join editor sessions from any other projects with the Switch, always have been able to do so. The crash only happens in this one big project, started happening about a month ago. Its a big project but not in size, it uses less than 40 out of the 100 memory bar limit

The similar reports I mentioned at the start of the post were the ones from @Wertandrew and @PledgedRanger you just linked. I believe I am having the same issue as them.
I decided to focus more on describing the weird behaviors instead of the project in hopes that Epic can more easily understand what is going on, since none of us seem to know how to replicate this in a new project.

BubbleBunz told me in DMs that he also had crashes in the exact same island depending on session type - sometimes it crashed when joining the editor only, after some tweaks it worked in the editor but crashed in private and public codes, which is terrible.

I had no idea Nintendo had those extended functions to allow earlier versions, and I see this is bad timing due to the recent updates exceeding the Switch’s default storage, but these things seem to have no connection to the issue. The crashes started to happen to me a few days after the 12th of September, but started even earlier to the people mentioned above.

This has to be a sneaky bug on Epic’s side, because as described in the last bullet point from the first post, once the Switch is in the editor session I can revert back to the main version with all the assets and do as many pushes as I want, but if at any moment I go back to the lobby and join the session again, it crashes.