Since the update to Minecraft PE version 1.6.0 my students keep getting booted from their built worlds. They get into their world but after a few seconds they get booted and returned to start screen. This is not a BETA version but through the app on the iPad. They created these worlds over the past 6 weeks. They are due to compete in an interschool competition tomorrow afternoon and cannot get in. We need a solution fast or they will be penalised before they even get to compete. HELP!!!!!
Linked issues
is duplicated by 7
relates to 4
Attachments
Comments 67

I'm not sure if I can help, but when they get booted do you mean the app crashes? Or does it say "disconnected from server?"
If it's at all possible, create a backup of one of the worlds then see if it works in beta, that might help. If the backup doesn't work then it could be their account or the app version, or the server it's saved on if it's a realm.
I'm not sure if I can help, but when they get booted do you mean the app crashes? Or does it say "disconnected from server?"
If it's at all possible, create a backup of one of the worlds then see if it works in beta, that might help. If the backup doesn't work then it could be their account or the app version, or the server it's saved on if it's a realm.
I mean the app crashes and sends them back to the home screen. They have tried creating a copy of the world but the same thing happens. How do they open in in beta if it is an iPad app? I think it is the app version update that is causing the issue. It isn't saved on a server, it saves on the iPad. Thanks for your help though.
I mean the app crashes and sends them back to the home screen. They have tried creating a copy of the world but the same thing happens. How do they open in in beta if it is an iPad app? I think it is the app version update that is causing the issue. It isn't saved on a server, it saves on the iPad. Thanks for your help though.
I have been having a similar problem of crashing out of the Minecraft app on my iPad Air 2 (non-server world). This happens when I am loading one of my worlds and also in another world when I move to an area of many mobs. This happens on both MCPE 1.6.0 and 1.6.1.
I just tried something on the same iPad Air 2 to see if I could reproduce in a new world (MCPE 1.6.1). I created a new world in creative/peaceful mode. Built a 7 by 7 by 4 high glass tank. Filled it with water.then started adding Tropical Fish (via eggs). When adding the 35th fish the Minecraft PE app crashed. I was able to re-enter the world, but on adding an additional 6 Tropical Fish the app crashed again. Here is a summary of attempts:
Started new creative/peaceful world, built glass water tank, adding Tropical Fish to tank and on 35th fish app crashed
reopened world, adding more Tropical Fish to tank and on 6th fish app crashed
reopened world, adding more Tropical Fish to tank and on 6th fish app crashed
reopened world, adding more Tropical Fish to tank and on 10th fish app crashed
reopened world, adding more Tropical Fish to tank and on 3rd fish app crashed
reopened world, adding more Tropical Fish to tank and on 12th fish app crashed
reopened world, world starts to appear, then app crashed
reopened world, world appears for less than a second, then app crashed
The current size of the world is 0.34 MBs.
same issue, both on ipad air 2, and iphone 6+
It also seems to be mob related - issue intensifies as cows, chickens and villagers grow. It started with the aquatics update. I wonder if it's related to the fish in the water.
here are 2 worlds that do this:
https://drive.google.com/open?id=1vEnNRDee3K4pl2oZLK2qYQWdWBjUOV34
same issue, both on ipad air 2, and iphone 6+
It also seems to be mob related - issue intensifies as cows, chickens and villagers grow. It started with the aquatics update. I wonder if it's related to the fish in the water.
here are 2 worlds that do this:
https://drive.google.com/open?id=1vEnNRDee3K4pl2oZLK2qYQWdWBjUOV34
Crashing still happening for me on 1.6.1, however by getting close enough to the crash point, then killing all tropical fish using /kill @e has seemingly ‘fixed’ my world.