mojira.dev
MCPE-137652

Cannot load or create any world in 1.17.30.20 Beta if using External Storage

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:

  1. Give 1.17.30.20 Beta a clean installation and switch File Storage Location into External.

  2. Create a new world.

Observed Results:

  1. The world fails to be created

Expected Results:

  1. World is created

Note a possible explanation as to why this happens is in MCPE-136660

Linked issues

MCPE-137663 Worlds have dissappeared Resolved MCPE-137667 Sign In issue world is not generating. No log in with microsoft account log in Resolved MCPE-137712 Failed to enter world. Resolved MCPE-137713 Not able to connect, play or see my worlds, and make new ones Resolved MCPE-137718 When creating the world, an error pops up Resolved

Attachments

Comments 20

john sinicki jr

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

Hank Wimbleton

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

[MCQA] v-magwar

On what device exactly did you experience the issue?

Thomas Lauth Kokholm

oneplus 8 pro

10 more comments

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+

Dylan Cleverley

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.

Thomas Lauth Kokholm

(Unassigned)

588266

Confirmed

Android

Android 11

1.17.30.20 Beta

1.17.30.21 Beta

Retrieved