Update: It seems that users who have reported the issues affecting the Switch version of Civilization VI have been getting official 2K customer service responses, one of which includes a temporary workaround.
According to reddit user Throwaway489er (via Eurogamer), an official response states that the dev team is aware of the issue and working on a solution, although at present there's no timeframe on a patch to resolve the problem. There is, however, a workaround for the issue which involves declaring war on the crash-causing civ before the end of your turn. Here are the details of the workaround from the customer service rep, as posted by Throwaway489er:
"A discovered known workaround is to declare war on the Civilization that is causing the crash right before you end your turn. This seems to alleviate the crashing in most instances. In order for you to know which Civilization is causing the crash, you'll have to pay attention to which Civ's turn it falls onto immediately before the crash happens. Once discovered, reload the save, declare war on that Civ and hit "Next Turn". I hope this workaround helped out. If you have any further questions or concerns, please don't hesitate to let us know!"
Let us know if you try this workaround and if it works for you below.
Original Story: The Switch version of Civilisation VI is a pretty good way to experience this world-building conquest title, but the latest update for the game has essentially rendered it unplayable.
As reported by Nintendo Life reader HeroponRiki, a bug has been introduced after the last update which causes the game to crash just as you're about to win a game. This issue appears to be occurring almost 100% of the time, and several threads have appeared on Reddit which feature users complaining about the problem. Nintendo Life contributor Yuri Litvinenko has also reported that he's experienced this problem with his copy of the game.
Reports have been flooding in since last month, and as of today, there's been no statement from 2K Games on when this will be fixed. We'll update this post if we hear anything, but in the meantime, drop us a comment if you've been impacted by this problem.