I was playing Minecraft with an IPad Pro on version 1.5.3, and I was trying to make a blaze grinder. I've lost three SETS of armor and died countless times thanks to this bug.
I was playing on a singleplayer world, not a realm.
I always thought they were supposed to be different languages, to make it seem random.
I made a post on this before it was labeled as a duplicate. So this is my account of the same bug.
This happened to three of my survival worlds already. All of them are deleted now, by me, which was kinda painful, to be honest. The most recent corruption was the final straw, which has led me to type out this complaint.
Let's go to that last survival world I was doing. I had a small dwelling with a pen next to it that contained a horse. A desert village with a desert temple was nearby. I had explored anything nearby. I had just discovered an abandoned mineshaft in my strip mine. These may have caused my player to go corrupt, but that's really unlikely.
I exited the world one day, and I re-entered the world the next day. And to my horror, I was standing at the place where I originally spawned, with nothing in my inventory. I went to creative and searched around. Everything I placed down was still there, but everything in my inventory was lost. I went into my copy, and the same thing occurred.
And yes, I did go into creative mode to get my stuff back, but it felt like I cheated, even though it should've been perfectly acceptable to do so. At the end, I deleted both the original world and the save as well. I'm planning to make another survival world, this time, whenever I leave the world, I'm going to make a save, and keep those saves until this bug is fixed, (or if I fill up my device's storage.) And while I believe that is a good plan, I still shouldn't have to do this. I shouldn't have to worry about my player resetting or my inventory disappearing.
P.S. Unfortunately, I forgot to take a screenshot. You'll just have to take me by my word
YES. I filed this bug out on this website as well! It seems like a common bug.
This problem is in 1.5.2 as well.