The game crashes and returns to the OS launcher when attempting to switch the storage location of a world from Application to External.
To reproduce this problem:
Begin playing in a Survival world that is currently using the application storage
Pause the game, then choose Settings -> Profile
Switch "File Storage Location" from "Application" to "External"
At this point the "File Storage Location" list will say "External" and will remain green, indicating it is the active widget, for approximately 3 seconds. During this time the game appears to be frozen. Then the widget will return to the normal "black on gray" colors, but the game is still unresponsive. It will stay this way for approximately 1 second, then the game will exit and return to the Android launcher/home screen.
The attached screenshots are of the settings screen before selecting "File Storage Location", after switching to "External" while still green, and after switching to "External" once the widget has returned to normal.
Linked issues
Attachments
Comments 7
migrated
Make sure that your micro-SD card is mounted, not full or corrupted, and that Minecraft has the necessary permissions to write to the SD card. These can all cause problems.
I experienced no trouble moving my files to external storage (Android 9 on Samsung phone, ample space, SD configured as external storage and mounted) I'm on beta 1.17.30.21, but no changes in save file management were announced (IIRC).
Make sure that your micro-SD card is mounted, not full or corrupted, and that Minecraft has the necessary permissions to write to the SD card. These can all cause problems.
I experienced no trouble moving my files to external storage (Android 9 on Samsung phone, ample space, SD configured as external storage and mounted) I'm on beta 1.17.30.21, but no changes in save file management were announced (IIRC).
Thank you for your report!
We're tracking this issue in MCPE-21167, 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.
Thank you for your report!
We're tracking this issue in MCPE-21167, 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.
@Baron Samedi I'm running on a Google Pixel 2, so I don't have an actual external SD card, but I do have emulated external storage. That storage has 4.6GB of available space and the world in question uses 236MB, so full storage isn't the issue. Furthermore, I tried making a new world in the application storage, then immediately tried to switch it to external storage, and the same behavior occurred. The new world is only 2.3MB.
I can switch the entire game to run out of external storage (by going to the application Settings -> Profile and switching File Storage Location to External) and create worlds in the external storage and everything works fine. Those worlds are visible in the expected location (/games/com.mojang/minecraftWorlds), and they are playable as normal. So it appears access to external storage, either because of app permissions or full/corruption is not the issue.
If I try to switch a specific world (let's call an example world "EtoI") from External storage to Application it says that it did so, and the world remains playable, but it doesn't actually move the world storage. If I exit Minecraft normally and restart the app, then switch the entire game from External to Application storage, the "EtoI" world doesn't appear in my worlds list. If I switch the game from Application back to External storage, though, the EtoI world reappears, and it's details say it still resides in External storage.
Lastly, @[Bot] Arisa closed this issue as a duplicate of MPCE-21167, WHICH WAS CLOSED 4 YEARS AGO AS INVALID WITH NO INVESTIGATION. That's extremely unhelpful.
@Baron Samedi I'm running on a Google Pixel 2, so I don't have an actual external SD card, but I do have emulated external storage. That storage has 4.6GB of available space and the world in question uses 236MB, so full storage isn't the issue. Furthermore, I tried making a new world in the application storage, then immediately tried to switch it to external storage, and the same behavior occurred. The new world is only 2.3MB.
I can switch the entire game to run out of external storage (by going to the application Settings -> Profile and switching File Storage Location to External) and create worlds in the external storage and everything works fine. Those worlds are visible in the expected location (/games/com.mojang/minecraftWorlds), and they are playable as normal. So it appears access to external storage, either because of app permissions or full/corruption is not the issue.
If I try to switch a specific world (let's call an example world "EtoI") from External storage to Application it says that it did so, and the world remains playable, but it doesn't actually move the world storage. If I exit Minecraft normally and restart the app, then switch the entire game from External to Application storage, the "EtoI" world doesn't appear in my worlds list. If I switch the game from Application back to External storage, though, the EtoI world reappears, and it's details say it still resides in External storage.
Lastly, @[Bot] Arisa closed this issue as a duplicate of MPCE-21167, WHICH WAS CLOSED 4 YEARS AGO AS INVALID WITH NO INVESTIGATION. That's extremely unhelpful.