Minecraft Playstation-4 crash error CE-38700-8 version 2.30

This report is invaild. Only Bedrock Edition exists for PS4, and PS4 doesn't even support Java!

You may want to update the version in your title to either 1.17.30 or 1.17.32 and not 2.3. 

I’m getting the same error on my Ps4 with one specific world. 

As if it is invalid report. Don't how but it selected Java edition instead of Bedrock; ok maybe I clicked it wrongly on my phone. Just small error.

My report won't considered just for that?

Don't give me this kind of comment. I just lost a almost year old world most likely because of an update that made the game (for which I paid for) defective. So I don't care too much if click a wrong tag or version. 

I will copy this report if it is so problematic now.

There is no need, a moderator will shortly move this ticket to the correct project section. 🙂

I have the same problem, i switch on the game, it loads, and after like 60+ seconds it drops dead.

Also the PS4, also the CE 38700-0 error message, also nothing help except i didn't try reinstalling the game. Looks like its a bug from the game's side.

I will try create an report So the bug will get futher notice. 

Thank you for your report!
However, this issue is Invalid for the bug tracker.

Crashes such as these are logged automatically by the game or server and investigated further by the development team internally, so they are not generally kept on the bug tracker.

If you can provide a list of steps that someone else can follow to consistently reproduce a crash then feel free to create a new report. Please be sure to always search for duplicates before creating any new report. Please see the Bug Tracker Guidelines for more information.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

I seriously can't believe it. I contacted "Mojang support" on Twitter and sent me to "Minecraft help center"; here I wrote my issue and "agent Thor" answered me and told me to check this bug tracker and write a report. I did all of this and finally my report... is invalid?!

My report is wrote in the wrong site...so it won't be considered?! I followed all of your instructions and that's it? Invalid?

Actually "invalid", pointless and inefficient is the support given to players. You clearly don't know how to provide support: you just make fool of players telling them to do things that finally are wrong.

So what am I supposed to do know? This is the wrong place to report this issue, so which is the right one, IF you have one? 

Your final advise is even useless: I already wrote the steps to reproduce this "bug". You just read the title and nothing in description? You may have set this report as resolved, but in the end it still remains UNSOLVED, and I still, after days, don't know how and why it actually happened nor how and if it can be solved.

As mentioned in the comment above, your device automatically sends diagnostic information to the developers about crashes. Each new release and hotfix contains fixes for various crashes based on that information.

Reports like this that just say that the game crashed, do not contain any useful information for fixing the issue, which is the purpose of this bug tracker. However, unless you had already read the Bug Tracker Guidelines, you would not know this before creating your report.

If you were able to provide a copy of the world that is crashing, that would be helpful. Unfortunately, with console devices such as the PlayStation, there may not be any way to upload the world somewhere that can be accessed by the developers for testing.

For technical issues you might visit Community Support for help, though there may not be anyone there who can solve this particular crash, but it might be worth asking.

As I wrote before, a supporter "agent" told me to come here, check for similar issues and eventually report it. I blindly followed his instructions.

Honestly, he should have told me before that devices sends automatically diagnostic information, I would have spared the time of writing here.

I also didn't read these "Bug Tracker Guidelines", since I didn't notice them because I was only concerned on reporting.

Furthermore, I didn't catch the meaning of your first comment: "Crashes like this are logged automatically...". That's because once I read the report was invalid I thought It wouldn't have been considered and that I wouldn't have received any help. That thought irritated me and didn't catch your comment's meaning.

My dissatisfaction is still towards "agents" that provide false information or don't provide the right ones, causing then situations of doubt and uncertainty.

You just did your job and gave the right informations you are supposed to provide. Thanks for the attention.

I'll just wait for new updates hoping that they'll fix the problem.

Thank you for your report!
We're tracking this issue in MCPE-143269, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
_{-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.}