A Possible Workaround
1. Leave the beta program and reinstall Minecraft (back to 1.17.10), Doing so may lose any worlds stored in Application data.(Note that opening any worlds that were opened in the beta may not work in the non-beta version)
2. Switch File Storage Location into External.
3. Rejoin the beta program and update and you may get legacy external file access.
Another possible work around to play external worlds in application storage for those who know how;
1. Go to your games/com.mojang/minecraftWorlds folder
2. Zip each world file and rename them from .zip to .mcworld
3. Switch to application storage and import those worlds.
I can't load any world's after updating to 1.17.30.20 beta.
I can't even create New world's is there any way to solve it
Steps to reproduce:
On an android 11 device do the following:
Give 1.17.30.20 Beta a clean installation and switch File Storage Location into External.
Create a new world.
Observed Results:
The world fails to be created
Expected Results:
World is created
Note a possible explanation as to why this happens is in MCPE-136660
Related issues
is duplicated by
Attachments
Comments


This is true for me as well, but only if worlds are in external storage.

Same, I used to have 27 world byt when update 1.17.30.20 Beta it all disappeared and left 1 world that I always play, but I can't even get in

Some worlds that I had were still there, maybe just 2 or 1 out of my 29 worlds, both had a missing texture picture

On what device exactly did you experience the issue?

oneplus 8 pro

Samsung Galaxy Tab S7 Plus

Nothing just happening... I tried all things to resolve the issue.... Because of tha even i can't find my world.... Because of this bug may my world will lost..... Please help me with issue of pufferfish. No new world generation. No old world find.
My device realme 7 pro
Android 11
Snapdragon 720G

@unknown: You seem to be looking for someone to help you explore your problem. For that you should visit the Community Support Discord, where you can interact with people knowledgeable about the game and how to use it on the various platforms it's available on.
Here on the bug tracker, what we do is help you prepare bug reports and submit them to the Mojang developers for an eventual fix. That is not an interactive process, and it usually takes weeks or months.

I also had this problem. When I opened the game yesterday, I noticed that the screen remained blank. I run on Samsung galaxy note 20 ultra, android 11. When I turned of display and turned back on the loading bar came up but asked me to log in. When attempting to it would say logging in but not do anything. So forced closed the app and tried again this time leaving it as is, not logging in, I attempted to start a new world and I got a msg stating that there was a problem generating world.

I have a MotoG (100) Android 11, and the game doesn't open worlds or create new ones, that is, it's practically useless.

It isn't just loading old worlds. Using the current beta the game will not create a new world, or load an existing one if i am using external storage. If i erase all game data it will let me create new worlds in internal storage, but if i try external storage nothing works again. This is with our without the caves and cliffs experimental mode toggled.

I second what John said. Everything is great with the game...unless you are trying to use external storage. The game essentially freezes when trying to switch to external storage, whether from the actual settings screen or the Create World screen.
If I'm lucky enough to actually get it to switch to external storage (waiting at least 10 minutes, if not more) then none of my resource packs, worlds, or addons show up.

@unknown: Yes, I figured that out when people kept reporting this, but I've been waiting for more information because I don't have MC on Android and couldn't test it myself. I'll ask another mod to take over this ticket now that we have consistent reporting about external storage being involved somehow.

Does the issue only happen when External Storage is being used?
In other words, does the issue also happen when not using External Storage?

yes actually i'm also using external storage

The game runs well when not using external storage. It's once you switch to external storage that you have issues.

@unknown: This is the bug tracker, not Community Support. Sometimes Community Support can help you solve a problem, but that is not what we do here. When people on the bug tracker find a workaround, they can add a comment here to share it, but usually we have to wait for Mojang to fix the bug. That typically takes weeks, so you need to be patient. You also need to stop repeating your demands for a solution, because we don't have one and your excessive comments are only getting in our way. Please use comments only to add new information that might provide clues to help Mojang solve the problem.

Attempted the possible workaround noted above. The game loaded perfectly and allowed me to switch to external storage; all of my worlds and packs were available once it switched from application storage. I closed the game and re-opened it but noticed it was slower to load than when I did the fresh install without external storage selected. It had been loading slow (2-3 minutes of loading screen) over the last couple of betas but I didn't realize how bad it was until I did the fresh public install.
I closed the game again after checking that my worlds and packs were still available and re-entered the beta via the Google Play store. After waiting for that to take effect, I updated and tried to open under the beta through the Google Play store. After waiting 10 minutes (blank gray screen) I manually closed out the game and tried opening it outside of the Google Play store instead. Waited another 10 minutes with a blank gray screen and it still didn't load.
It really does appear the external storage selection is causing some kind of hangup with the loading on both the public and beta versions of the game.
I'm on Android 11 on a Samsung Galaxy Note 10+

I figured out that the storage permission only gives access to media and the Android/data folder.
Minecraft could just edit the manifest to allow all files and release an Android-only update.

The author of the merged MCPE-137848 additionally mentions being incapable of logging in to his Microsoft account, which is not a typical feature of this bug - it sounds more like something that he should contact Community Support about.