Chris

I've noticed this case hasn't progressed much since I opened this issue 2 years ago. Mojang never responded directly to my suggested resolution (or vital evidence), and it's now buried deep in this thread and/or links to mis-closed or mis-merged cases. So, in hopes of directing Mojang to the actual problem... here it is again:

1. The problem occurs when,
-A Mincraft update adds a new mob.
-The new mob spawns in location that the user has previously edited. For example, I built a structure where now (after an update) a piliger tower spawned (a newly added mob at the time). That location then developed a huge missing chunk/s.

2. This issue only happens on my "heavily" edited stock worlds (vanilla with no mods). Since this means the issue only may occur on user's deeply time-invested projects, I believe it should now be Mojang's best critical interest to fix this issue.

3. As an interim solution, I'm again requesting a tutorial on how to stitch in a chunk. If we have this procedure, we all could take the chunk coordinates from a good backup world, and then replace those coordinates in the world after it has been updated, thus overwriting the corruption in the location that the update caused.

I used to have that problem. The problem happened to me when I loaded into realms and servers on a bad connection, it would usually go away on a stronger connection.

Copied my mcpe world from "/MC/com.mojang/minecraftWorlds" to new phone, and now it has these same chunk bug issues. Copied same world to PC bedrock and it works fine. Saved from PC and put back on phone... missing chunks again.  So seems to be a bug tied to mcpe? This bug is a game breaker and extremely old... please fix mojang!

@Poyraz Sivirikaya - Ok I'll check those areas out.

it's probably because you're playing on a snapshot, snapshots are very unstable compared to actual versions, so i recommend you to play 1.16.4

Snapshots seem to commonly have these issues, try playing Release 1.16.4 instead of the snapshot

Idk why mojang won't address this issue. I brought it up last October when it started, and again a few months later, but they have just continually given me the run-around with zero attempt at a solution (see MCPE-60952 that I created).

I have many examples, and they all look similar to the screenshots you guys have attached here. And yes, the worlds are all completely vanilla.

What I do know is this:

1. The worlds work fine in MCPE versions prior to v1.14.1

2. Sideload an older version version of MCPE and you're off and running

3. Or, open the world in Windows Bedrock (any version including v1.16.10) and all works fine

4. Yes, the above only works if you were lucky enough to have saved the ....MinecraftWorlds\blaHbLAhblAH folder before the bug corrupted it in October.

5. I've tried transferring the working world from Windows Bedrock over to MCPE, but the bug destroys things back to about 1/3 default terrain, 1/3 missing chunks, and 1/3 remnants of the developed world

So, since mojang isn't offerring any kind of recognition or resolution to this specific bug, I propose posting a different question, which is....

Devs, if we have a world that works fine in Windows Bedrock v1.16.10 and MCPE prior to v1.14.1, but anything after MCPE v1.14.1 destroys the world, how do we transfer our currently working world over to MCPE v1.16.10 or higher?

 Thank you for your time...

I have been around and around with Mojang on this ticket. They've confirmed an issue with large maps losing chunks when updating. It has something to do with new mob structures being forced on a map. A temporary solution has been to downgrad to Minecraft - 1.12.1. This temporary fix has worked on all maps which experience the lost chunks. So now the only way to use your large map with the latest version is allegedly to meticulously cut out all the chunks you've edited on your map and paste them into the new version of the map... using a map editor. 

I haven't tried the editor yet as it looks quite time intensive, but I will report back when I make progress. It's unfortunately been near impossible to get timely help or non-conflicting information from Mojang.

I have been around and around with Mojang on this ticket. They've confirmed an issue with large maps losing chunks when updating. It has something to do with new mob structures being forced on a map. A temporary solution has been to downgrad to Minecraft - 1.12.1. This temporary fix has worked on all maps which experience the lost chunks. So now the only way to use your large map with the latest version is allegedly to meticulously cut out all the chunks you've edited on your map and paste them into the new version of the map... using a map editor. 

I haven't tried the editor yet as it looks quite time intensive, but I will report back when I make progress. It's unfortunately been near impossible to get timely help or non-conflicting information from Mojang.

Your issue sounds like mine. I've learned that it's not due to a corrupt world, but rather something to do with the latest update. For example, copying your world to an older version or Windows 10 desktop will likely work fine. 

Reference --> MCPE-60952

Sorry for the bad video quality, I had to record my phone with my Nintendo Switch playing the captured gameplay recording.

Forgot to mention... this issue has only been occurring since (12.12.2018) after the last update. 

My son posted this trouble ticket. I will resubmit formally.

-Chris

Same here.

Samsung Tab 4, Android 5.1.1 working fine a day or two ago.

Hangs on start.

Reset, un-install and delte /games/com.mojang then re-install did not fix it.

When it starts up there is some https traffic to the internet from the app to to some IP's without a reverse DNS and then nothing, it hangs.

Kids iPads and my iPhone are fine.

Just a quick 'me too'.

Was playing the game yesterday, tonight it does not work.

Tried:

• Restarting tablet (Samsung Tab 4)

• Backed up and deleted worlds folder

• Uninstalled app, deleted /games/com.mojang completed, restarted

• re-installed app.

Still no-go.

Watching the network the game does call home when starting up for about 5-10 seconds, then no traffic and it appears to be hung.

Version 1.4.4.0 per the other reports.

Kids are still playing on the iPads just fine, my iPhone is fine but Android dead in the water.

Tried setting date to 1st June 2018 as it was mentioned somewhere that it might be a date related issue / bug but that made no difference, although I could reminisce about last month for a wee while. 🙂 

Power abruptly went off on my Apple TV 4. Upon reload my profile was changed back to Steve and my game was corrupted.

u sounld put human villagers not the squild villager.

ok