Let's get with the current situation that's been bugging me for the past few days. the whole 'reverting your Minecraft game to it's retail version after being logged out of the profile'. It hasn't happened before, only after being updated to the Trails and Tales update. Before it occured, I was updating the game, only consisting of 300MB. Once that's finished, I turned my wifi off to get rid of the pesky lag that's been happening (don't want my Minecraft freeze up with unloaded chunks just because I got disconnected with the wi-fi or something) and opened up Minecraft to play the new update. Through the loading screen, I was met with an error causing me to get logged out of my profile, and upon returning, seeing my Minecraft Bedrock game turn into the retail 'Minecraft: Playstation 4 Edition'. When running it again, I wasn't able to play it, was forced to update it, with the size being 2GB to 3GB, give or take. It was somewhere 2.3GB. This, however, was resolved with a 'rebuild database' and 'restore licences' methods, but I'm not sure how long this 'solution' will persist.
Now, the other issue, crashes. Just 'CE-34878-0' crashes. It happened during quitting a world, breaking a block, and just running around. Three times in one day.
Comments 3
Are you saying that the game reverts to the PS4 edition every time you try to load it, or that it did so only once?
The crashes would be a separate issues and not something we would track on the bug tracker unless you can give specific steps to reproduce. The game already sends crash reports automatically.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
So, I'm just gonna add something here.
The three crashes themselves have a timeline.
Technically, there's four crashes, but the most notable one is the three consecutive crashes.
First crash happened on 20:50, June 9th.
Second crash happened on 21:01, June 9th
Third crash happened on 21:58, June 9th
So, more or less an hour before it crashes.
And I got my fourth (5th in total) crash just recently. 22:50, June 10th.