[MCPE-12049] Error "<World Name> can't be opened" when creating or opening new world

I am unable to open worlds on a new budget-brand tablet running MCPE 13.0 and Android 4.4.4 - it's a Spidotech Sleek W1:

http://spidotech.com/tablet.html

What I expected to happen was...:
A new or existing world should be loaded.

What actually happened was...:
The error '"<World Name>" can't be opened' is seen every time, even though the world is created on the SD card.

Steps to Reproduce:
1. Tap 'Play'
2. Tap 'New World' or any existing world
2a. Configure the new world as desired
3. The world begins to load, and the error is encountered

Additional info:
I tried removing all of these created worlds and replacing with a known good world from a working Android tablet, but this one wouldn't open either. All other running apps have been closed. OS is up-to-date.

Please let me know what other information I can provide - I did check that the spec of this tablet meets the minimum spec for MCPE, so I don't think hat should be an issue here.

I have an identical tablet which I will try to reproduce the problem on this evening, which should at least suggest whether or not it is device-related.

Comments 24

Gary Kemp 2015-12-12T17:08:57Z

Having browsed a few forum threads and other similar bugs, I have noticed that storage could be a factor here. FWIW, this model of tablet has Device memory, 'Internal SD Card' memory, and an expansion slot for an SD card. By default, I think it installs Minecraft on the internal SD card. I'll see if it is possible to install directly to device memory.

migrated 2015-12-12T17:08:57Z

Gary Kemp 2015-12-13T22:13:17Z

I am able to join a local multiplayer world on this tablet without error, so I guess this points towards a local file issue.

migrated 2015-12-13T22:13:17Z

I am able to join a local multiplayer world on this tablet without error, so I guess this points towards a local file issue.

Gary Kemp 2015-12-18T09:23:39Z

Have just set up the second tablet and I am experiencing the same issue on that one - version 13.1 Alpha.

14 more comments

migrated 2015-12-18T09:23:39Z

Have just set up the second tablet and I am experiencing the same issue on that one - version 13.1 Alpha.

Phil Rogers 2015-12-23T21:39:14Z

Reproduced from MCPE-7852 (which was closed, even though it didn't fix the problem)

Fresh install of MCPE 0.10.4 on an Android tablet. Starts up ok. Click Play and then New. Enter details of World and click Create World!
Message displayed: "My World" can't be opened.
Tried every possible combination of settings but makes no difference.
Tried on similar tablet and it works ok. Examined tablet storage by connecting to a PC.
Looked in \games\com.mojang\minecraftWorlds
All the worlds that we tried to create had folders containing files.
However, none of these worlds are listed in the game when Play is clicked.
Did same on other tablet and noticed that there were more files in each created world.
Copied some of these worlds to the non-working tablet. Started MCPE and clicked Play. Now shows the copied worlds in the list. Selected a world but still got the "My World" can't be opened message.
Ran PocketMine server on my PC. Both tablets show the server world in the list and when selected, they both connect and work as expected.
Issue appears to be in creating/loading local worlds.
Files in a world folder on "non-working" version:
======================================
db (folder)
lost (folder)
contains 17 x .log files numbered from 000003 to 000051, going up in steps of 3, plus MANIFEST-000001
CURRENT
LOCK
LOG
LOG.old
MANIFEST-000001
Files in a world folder on "working" version:
==================================
level.dat
db (folder)
000005.ldb
000379.ldb
000380.ldb
000381.ldb
000382.ldb
000383.ldb
000385.ldb
000386.ldb
CURRENT
LOCK
LOG
LOG.old
MANIFEST-000384
Both tablets are running Android KitKat 4.4.2 and the same version of MCPE (v0.10.4 alpha)

All updates applied as they have been released, and none of them came close to fixing the problem. Have got 0.13.0 now, and still can't open worlds.

migrated 2015-12-23T21:39:14Z

Reproduced from MCPE-7852 (which was closed, even though it didn't fix the problem)

All updates applied as they have been released, and none of them came close to fixing the problem. Have got 0.13.0 now, and still can't open worlds.

tristan williams 2015-12-27T02:00:04Z

Have a valuepad with an internal SD card. Running android 4.4.2 and latest minecraft app. Please help us figure this out!

migrated 2015-12-27T02:00:04Z

Have a valuepad with an internal SD card. Running android 4.4.2 and latest minecraft app. Please help us figure this out!

Alawnely 2015-12-27T08:33:45Z

I think your device is out of memory.

migrated 2015-12-27T08:33:45Z

I think your device is out of memory.

Luke Deverill 2015-12-31T10:08:58Z

We have a similar issue here with our BTC Flame, this issue was raised over a year now. Don't sell a product that doesn't work as advertised. What is being done to resolve it?

migrated 2015-12-31T10:08:58Z

We have a similar issue here with our BTC Flame, this issue was raised over a year now. Don't sell a product that doesn't work as advertised. What is being done to resolve it?

deirdre jones 2016-01-03T22:01:25Z

Have a very disappointed 8 year old on my hands now. As said before, a simple google search shows that this is not a new issue. Why is something being sold that doesn't work? We have an android smartpad lite tablet. When will this be fixed!!!

migrated 2016-01-03T22:01:25Z

David Etheridge 2016-01-14T00:27:28Z

We have a brand new BTC Flame tablet running Android 4.4.4, purchased for our son as a Christmas present. Yesterday installed MCPE from Google Play, as a reward for having blood taken. Any attempt to create a new world gets the "[My World] can't be created" error. In other words, the game is useless and not fit for purpose unless this bug can be fixed.

migrated 2016-01-14T00:27:28Z

Gary Kemp 2016-02-28T18:54:21Z

Hi, has this been looked into at all?

migrated 2016-02-28T18:54:21Z

Hi, has this been looked into at all?

AMAN4700 2016-06-02T02:51:04Z

Does this bug still appear in 0.14.3? Please respond.

migrated 2016-06-02T02:51:04Z

Does this bug still appear in 0.14.3? Please respond.

[Mojang] Mega_Spud (Jay) 2017-08-21T11:08:26Z

This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)

[Mojang] Mega_Spud (Jay) 2017-08-21T11:08:26Z

This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)