I went to update my official Minecraft 1.21.30 my game entered the beta version and I'm playing in the beta, here are the images for you to see
Linked issues
is duplicated by 11
BDS-19776
atualização errada - Incorrect Update
Resolved
BDS-19779
Account updated to Beta without opt in
Resolved
BDS-19784
Minecraft automatically going into beta on Chromebook versus.
Resolved
BDS-19788
Cannot login to world or realm
Resolved
MCPE-187307
Bedrock updates to beta version without beta participation
Resolved
Attachments
Comments 23
migrated
Final Update
The Play Store now has both the retail version 1.21.31 for those who aren't in the Beta program and the Beta version 1.21.50.22 for those who are. This resolves the issue.
Players who do not currently have the correct version installed should now be able to obtain the correct one from the Play Store either by updating manually or waiting for Auto-update to download it. However, players leaving the Beta program might need to uninstall and reinstall the game in some cases. Please contact Mojang Support if you need further help.
ATTENTION
Until this can be reversed, I recommend that you DO NOT UPDATE UNTIL FURTHER NOTICE. If you've already updated, DO NOT OPEN ANY WORLDS. Any worlds that are opened in 1.21.50.20 Beta will be upgraded to that version and you will not be able to open them in 1.21.30 when you've reinstalled it. You'll have to wait until the 1.21.50 full release to open them again.
UPDATES
10/10/2024 02:00 UTC
The Google Play Store is now offering an "update" that restores the app to the 1.21.31 version. Players who had this problem can simply go into the Play Store app, search for Minecraft, and touch Update to reinstall it.
After reinstalling, the game will show the correct version number in the lower right corner of the main menu, but the panorama behind it might still be the Beta one. This will not affect gameplay and should correct itself the next time you launch the game.
10/10/2024 16:00 UTC
For players who are not in the Beta program but installed the erroneous Beta version: It's now safe to turn automatic updating for Minecraft back on and update the game. This will reinstall the regular 1.21.31 Hotfix retail version. If you loaded any worlds while the Beta version was installed, you will either have to replace them with a backup copy or wait until an update to the regular 1.21.5? release is available (which I imagine will be some weeks in the future).
For players who are in the Beta program and updated from the Play Store but found that the regular 1.21.31 was installed instead of the 1.21.50.20 Beta release: Mojang is rushing to fix the problem by releasing a new hotfix Beta version. When it's ready, the Play Store will show you that an update is available; all you need to do is update and everything should go back to normal for you. I believe they're planning for that to be available within about 1 day.
Similarly, if you update, it will automatically become the beta version...
(※App Ver.1.21.50.20, Device used: Sony SOG09 Xperia5Ⅳ Android14 / Translation used)
Additional note→ The regular version has been released on Google Play and has been reverted to the regular version.
(※App Ver.1.21.31.05, Device used: Sony SOG09 Xperia5Ⅳ Android14 / Translation used)
(※This is personal, but I'm glad I made a copy of the world after the update. Instead of playing the main world, I made a copy of the main world and played it. I hope this is helpful to everyone😊)
I want to advise anyone not participating in the beta to turn off auto updates for Minecraft for now. Even if you choose not to update manually, there is a chance that the auto-update may activate and install the beta version (this happened to my Pixel 8 Pro)
In the future, there may be more mistakes like this, so after updating, try test playing the game in a copy of the main world without opening the main world... (I know it's a bit late now...) (※Translated)
@unknown: I'm sorry, but unfortunately it's impossible to revert worlds to an earlier release. The amount of work it would take to plan, design, code, and test that functionality would take so long that it would hold up later releases, and this kind of problem just doesn't happen often enough to make it worthwhile.
I have the Android version but I really only use it for bug testing, so I don't know if there's any way to back up worlds on the platform. If there is, I recommend making regular backups to protect against not only this problem, but random glitches in the network or in Android that might corrupt your worlds.
@unknown you might be able to restore your world, by converting it back to 1.21.31 with https://chunker.app