Sometimes when I try to load a saved world, the app closes without an error message. It continues to run in the background, but going back to the app returns me to the Mojang intro screen.
It may somehow be related to memory. It happens with worlds that have been played in a lot (11 MB or greater on my iPhone 6S, it seems), and reducing the render distance can help.
I can generate new worlds all day long. I have made hundreds trying for new seeds and never seen a crash with it. It's strictly limited to loading a saved world. When it crashes, it force-closes the app with no error message.
The world can eventually be loaded by completely quitting and restarting the app and trying again, but it can take several tries. Other times there is no problem at all.
I never play with other apps open in the background, so it's not that.
If there is a way to get crash reports from an iPhone without jailbreaking, I'm happy to do so.
Apologies if this is a duplicate. I searched high and low, but many crash issues lack detail and have terrible summaries.
Comments 7
Actually, I haven't experienced this problem in a while. I thought my family had experienced it in 0.14.2, but I may owe an apology. I would amend it to affecting 0.14.0, because that is the only version I can be absolutely certain of, but it isn't available on the list. The timing in my memory is a little fuzzy. If there were any crash fixes included in 0.14.1 or 0.14.2, I would say this is resolved.
Are the saved worlds super-flat?