I can concur. The same issue is plaquing my account. I do not go through breaking down the same step analysis to reproduce scenario, since mine is literally the same than what OP is reporting and showing on the uploaded video.
Additional information I want to provide is that the problem started for me when I had issues with my saves on Elden Ring. The only solution to fix that was doing a local wipe of all save games from my Xbox Series X. I did that and it fixed my Elden Ring issue. Unfortunately, as a result it removed my local save game from my local console. I then went right ahead to resynchronize with the cloud to re-download the save file to which the same issue happened that the OP observed. Went through all of the restart cycles, and even re-installed Minecraft, and the problem persists.
I then fired up my old Xbox One, which I have not been using in a long time, hence did not have an up to date local save either. The same behavior happened on the Xbox One as well, where the game crashed to Home upon Synchronization.
I then went further and tried creating a new World on my Series X. That worked just fine and is playable. Went ahead and tried synchronizing to my Xbox One, which also worked without crash.
Finally, I tried synchronizing a test small test world from the cloud to my Series X, which was only ~7MB in size. Surprisingly, that synchronization worked without issue.
Thus, I believe that the file size plays a role in the synchronization crash. OP mentioned that his file size is 188.3 MB, while mine is ~ 280 MB (have not loaded up Minecraft in a while).
This is really concerning for me since I am about to hit the end of my Game Pass Unlimited subscription, and am not sure I want to keep it – especially seeing all of these ongoing issues with Cloud Storage. Sadly, I fear that this will mean that I will likely lose my long-term survival world for a bug, that does not even seem to be confirmed.
Edit: I should add that this problem started to occur for me during Version 1.18 already, and upgrade to 1.19 did not help/resolve anything.
Ken-Warros
I can concur. The same issue is plaquing my account. I do not go through breaking down the same step analysis to reproduce scenario, since mine is literally the same than what OP is reporting and showing on the uploaded video.
Additional information I want to provide is that the problem started for me when I had issues with my saves on Elden Ring. The only solution to fix that was doing a local wipe of all save games from my Xbox Series X. I did that and it fixed my Elden Ring issue. Unfortunately, as a result it removed my local save game from my local console. I then went right ahead to resynchronize with the cloud to re-download the save file to which the same issue happened that the OP observed. Went through all of the restart cycles, and even re-installed Minecraft, and the problem persists.
I then fired up my old Xbox One, which I have not been using in a long time, hence did not have an up to date local save either. The same behavior happened on the Xbox One as well, where the game crashed to Home upon Synchronization.
I then went further and tried creating a new World on my Series X. That worked just fine and is playable. Went ahead and tried synchronizing to my Xbox One, which also worked without crash.
Finally, I tried synchronizing a test small test world from the cloud to my Series X, which was only ~7MB in size. Surprisingly, that synchronization worked without issue.
Thus, I believe that the file size plays a role in the synchronization crash. OP mentioned that his file size is 188.3 MB, while mine is ~ 280 MB (have not loaded up Minecraft in a while).
This is really concerning for me since I am about to hit the end of my Game Pass Unlimited subscription, and am not sure I want to keep it – especially seeing all of these ongoing issues with Cloud Storage. Sadly, I fear that this will mean that I will likely lose my long-term survival world for a bug, that does not even seem to be confirmed.
Edit: I should add that this problem started to occur for me during Version 1.18 already, and upgrade to 1.19 did not help/resolve anything.