Syncing/corrupted world issues

That is what has been happening to me. One console, but it tells me it is either not synced properly or is corrupt. I have been waiting for it to decide to work for a month but no dice. I have a world that is about 860ish MB. However, it displays the world as being 2.7 GB. It arose after I did a factory reset on my console to fix an Xbox error. It still shows up, but it cannot sync and cannot load.

This is happening to me as well and I can not delete the saved worlds files at all. Any insight on how to reset everything. This is for my son, he is not happy.

This is happening to me as well and I can not delete the saved worlds files at all. Any insight on how to reset everything. This is for my son, he is not happy.

Anyone had any luck? It’s doing a lot of syncing when I load the game and every now and again asks whether to load from the console or the cloud depending on whether I wish to load the old or newer version of the world.

Anyone had any luck? It’s doing a lot of syncing when I load the game and every now and again asks whether to load from the console or the cloud depending on whether I wish to load the old or newer version of the world.

I haven't tried in a few days. Would you recommend I do?

I haven't tried in a few days. Would you recommend I do?

I tried anyways. Still no change.

I tried anyways. Still no change.

MCPE-35364 - This problem sounds like it is the same as mine. Status is still open since 10 July. It's taking a while to resolve.

MCPE-35364 - This problem sounds like it is the same as mine. Status is still open since 10 July. It's taking a while to resolve.

Yeah, I've been waiting to play for over a month, but still no word on the status of fixing this issue and related ones. Hopefully it all gets fixed in 1.7.

Yeah, I've been waiting to play for over a month, but still no word on the status of fixing this issue and related ones. Hopefully it all gets fixed in 1.7.

Any new information?

Any new information?

No. Is Mega Spud a developer? Maybe if we ask him?

No. Is Mega Spud a developer? Maybe if we ask him?

How would we go about that?

How would we go about that?

This should be fixed in the 1.7 beta version, but we'll leave this (and the related tickets) open until the stable version of 1.7 is released. (No ETA, sorry!)

This should be fixed in the 1.7 beta version, but we'll leave this (and the related tickets) open until the stable version of 1.7 is released. (No ETA, sorry!)

Thank you Spud! That is great to hear.

Thank you Spud! That is great to hear.

I noticed that the 1.8 beta was released recently. I am thinking that 1.7 will be released soon.

I noticed that the 1.8 beta was released recently. I am thinking that 1.7 will be released soon.

I hope so. It’s been a long wait.

I hope so. It’s been a long wait.

1.7 was released. Still not working. I tried two times, but it gave me the same message as before.

1.7 was released. Still not working. I tried two times, but it gave me the same message as before.

That’s disappointing. I’ll try when the status says resolved.

That’s disappointing. I’ll try when the status says resolved.

These world-save issues are beginning to pile up. If these don't get fixed soon, it could become a bit of a disaster. Lots of worlds have likely been lost in the time that these issues have been unfixed.

These world-save issues are beginning to pile up. If these don't get fixed soon, it could become a bit of a disaster. Lots of worlds have likely been lost in the time that these issues have been unfixed.

Hey, it would probably be a good idea to remove the 1.7.0.9 fix version label as it remains unfixed.

Hey, it would probably be a good idea to remove the 1.7.0.9 fix version label as it remains unfixed.

Ean,

Mega Spud has commented on the other bug report to say it should be fixed now with 1.7. Will try later. Fingers crossed.

Ean,

Mega Spud has commented on the other bug report to say it should be fixed now with 1.7. Will try later. Fingers crossed.

Adding the request for feedback on this here too:
Please could you try syncing your larger world saves and let me know? Patience is the key, especially when using slower connections, and you might need to open the world in 1.7 for it to trigger the upload sync.

From our tests, it might take some time for large saves to sync correctly (20+ minutes), and you might encounter the message "your other console is taking to long to sync". Just press "Try again" (not sync current data) and it should eventually upload to the cloud.

It might take another 10+ minutes to download the world from the cloud, and at some time the progress bar might freeze for a couple of seconds but the transfer should complete.

Adding the request for feedback on this here too:
Please could you try syncing your larger world saves and let me know? Patience is the key, especially when using slower connections, and you might need to open the world in 1.7 for it to trigger the upload sync.

From our tests, it might take some time for large saves to sync correctly (20+ minutes), and you might encounter the message "your other console is taking to long to sync". Just press "Try again" (not sync current data) and it should eventually upload to the cloud.

It might take another 10+ minutes to download the world from the cloud, and at some time the progress bar might freeze for a couple of seconds but the transfer should complete.

How do I initiate the sync? I tried loading my world the day 1.7 came out but it still gave me the response "Your world either did not sync fully or is corrupted." It is just the one world that does it.

How do I initiate the sync? I tried loading my world the day 1.7 came out but it still gave me the response "Your world either did not sync fully or is corrupted." It is just the one world that does it.

Sorry for constantly spamming this thread. I tried to load my big world (after syncing all my other worlds) and still no dice. I then waited a bit and tried and again and it still failed. I feel it is more related to the bug MCPE-35364, notably the original version that was fixed in August with 1.6.1. It behaves in much the same way but without the crashing aspect. The error displayed is the same and it also makes the thumbnail a black and white default.

Edit: It actually is shown in the last screenshot of MCPE-35364.

Sorry for constantly spamming this thread. I tried to load my big world (after syncing all my other worlds) and still no dice. I then waited a bit and tried and again and it still failed. I feel it is more related to the bug MCPE-35364, notably the original version that was fixed in August with 1.6.1. It behaves in much the same way but without the crashing aspect. The error displayed is the same and it also makes the thumbnail a black and white default.

Edit: It actually is shown in the last screenshot of MCPE-35364.

It has been possible in some cases to recover the saved game, but if the corrupted save is already synced to the cloud, there's unlikely to be a complete save available, unfortunately. Here's a little bit of information about how syncing the games should work:

The upload process on the console is automatic and runs as a background process. If you have more than one console the "Your other console is taking to long to sync message, Try again message" might appear on your second console, if the world is still being uploaded. You can not monitor the upload process, as it runs on the system as a background process. Except by looking at this message from a different console.

If the world is fully present as a local save (the local save data is not deleted by for example a reinstall), you can trigger the local save to be uploaded to the cloud by creating a copy or possibly opening the world again. This copy will then in the background be uploaded to the cloud by the background process from the system. In case your world is greyed out, it most likely does not have the local save data (or incomplete) and might download the corrupted data from the cloud instead.

In 1.7 there is a change that should prevent the issue from occurring again with large worlds.

It has been possible in some cases to recover the saved game, but if the corrupted save is already synced to the cloud, there's unlikely to be a complete save available, unfortunately. Here's a little bit of information about how syncing the games should work:

The upload process on the console is automatic and runs as a background process. If you have more than one console the "Your other console is taking to long to sync message, Try again message" might appear on your second console, if the world is still being uploaded. You can not monitor the upload process, as it runs on the system as a background process. Except by looking at this message from a different console.

If the world is fully present as a local save (the local save data is not deleted by for example a reinstall), you can trigger the local save to be uploaded to the cloud by creating a copy or possibly opening the world again. This copy will then in the background be uploaded to the cloud by the background process from the system. In case your world is greyed out, it most likely does not have the local save data (or incomplete) and might download the corrupted data from the cloud instead.

In 1.7 there is a change that should prevent the issue from occurring again with large worlds.

So I just load up minecraft and wait a while for it to retrieve info automatically?

So I just load up minecraft and wait a while for it to retrieve info automatically?

Hi Mega Spud,

If the world was greyed out but now is now no longer greyed out following the copy process,  does it mean it's now all ok?

Hi Mega Spud,

If the world was greyed out but now is now no longer greyed out following the copy process,  does it mean it's now all ok?

Hi Jay,

Does update 1.7.1 now address this problem?

Hi Jay,

Does update 1.7.1 now address this problem?

Yes this should be fixed now in 1.7.x - large worlds should sync correctly, but you will need to update the sync process using the steps described above. If in doubt, please make a backup/copy of any worlds beforehand.

Yes this should be fixed now in 1.7.x - large worlds should sync correctly, but you will need to update the sync process using the steps described above. If in doubt, please make a backup/copy of any worlds beforehand.

Hi Jay,

Loaded the world last night and there were no issues - no messages on corruption or syncing problems. Essentially, it loaded normally. However, when I went back to play at a later time, the world save is now greyed out with a smaller file size. I did not try loading it as I did not want to compromise the saved file.

Hi Jay,

Loaded the world last night and there were no issues - no messages on corruption or syncing problems. Essentially, it loaded normally. However, when I went back to play at a later time, the world save is now greyed out with a smaller file size. I did not try loading it as I did not want to compromise the saved file.

@unknown Could you just confirm which version you are using, and if you are in the beta or not please?

Also, did the game crash at all, or did you power off the device without exiting the world?

@unknown Could you just confirm which version you are using, and if you are in the beta or not please?

Also, did the game crash at all, or did you power off the device without exiting the world?

Version 1.7.1. Not in beta mode. Game saved normally with a normal world save picture. Only when playing again a few hours later, the world save image was greyed out with a smaller world size.

Version 1.7.1. Not in beta mode. Game saved normally with a normal world save picture. Only when playing again a few hours later, the world save image was greyed out with a smaller world size.

Ok thanks. Does the world actually open ok? Is it just the thumbnail that is not showing correctly?

Ok thanks. Does the world actually open ok? Is it just the thumbnail that is not showing correctly?

The world opens but with the message unable to sync properly and file may be corrupted. On saving, the thumbnail reverts back to normal. But if I shut down the console and restart, the thumbnail goes grey again. The previous world I lost, it would do exactly the same until one day the world name changes to some random letters and the file size becomes 0.1mb. At this point, the world will not load. It hasn’t reached that stage for this current world.

The world opens but with the message unable to sync properly and file may be corrupted. On saving, the thumbnail reverts back to normal. But if I shut down the console and restart, the thumbnail goes grey again. The previous world I lost, it would do exactly the same until one day the world name changes to some random letters and the file size becomes 0.1mb. At this point, the world will not load. It hasn’t reached that stage for this current world.

It now appears stable. Great. I hope the problem doesn't return with the major updates coming.